core-lightning/common/status_wire.csv

#include <common/per_peer_state.h>
#include <common/node_id.h>
#include <common/status_wire.h>

msgtype,status_log,0xFFF0
msgdata,status_log,level,enum log_level,
msgdata,status_log,peer,?node_id,
msgdata,status_log,entry,wirestring,

msgtype,status_io,0xFFF1
msgdata,status_io,iodir,enum log_level,
msgdata,status_io,peer,?node_id,
msgdata,status_io,who,wirestring,
msgdata,status_io,len,u16,
msgdata,status_io,data,u8,len

msgtype,status_fail,0xFFF2
msgdata,status_fail,failreason,enum status_failreason,
msgdata,status_fail,desc,wirestring,

msgtype,status_peer_connection_lost,0xFFF3

msgtype,status_peer_billboard,0xFFF5
msgdata,status_peer_billboard,perm,bool,
msgdata,status_peer_billboard,happenings,wirestring,
# Note: 0xFFFF is reserved for MSG_PASS_FD!
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it's even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-06-03 20:11:25 +02:00			`#include <common/per_peer_state.h>`
wire: move remaining bitcoin functions out to bitcoin/ files. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-05-16 03:29:05 +02:00			`#include <common/node_id.h>`
status: generate messages rather than marshal/unmarshal manually. Now we have wirestring, this is much more natural. And with the 24M length limit, we needn't be so concerned about dumping 64k peer messages in hex. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-08 02:25:12 +01:00			`#include <common/status_wire.h>`

wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,status_log,0xFFF0`
bolt-gen: use 'enum' instead of 'e:' prefix for enums use 'enum ' in wirespec instead of 'e:' as an indicator that a field is an enum. 2019-07-24 06:20:04 +02:00			`msgdata,status_log,level,enum log_level,`
common: allow subdaemons to specify the node_id in status messages. This is ignored in subdaemons which are per-peer, but very useful for multi-peer daemons like connectd and gossipd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-11-17 12:42:33 +01:00			`msgdata,status_log,peer,?node_id,`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgdata,status_log,entry,wirestring,`
status: generate messages rather than marshal/unmarshal manually. Now we have wirestring, this is much more natural. And with the 24M length limit, we needn't be so concerned about dumping 64k peer messages in hex. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-08 02:25:12 +01:00
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,status_io,0xFFF1`
bolt-gen: use 'enum' instead of 'e:' prefix for enums use 'enum ' in wirespec instead of 'e:' as an indicator that a field is an enum. 2019-07-24 06:20:04 +02:00			`msgdata,status_io,iodir,enum log_level,`
common: allow subdaemons to specify the node_id in status messages. This is ignored in subdaemons which are per-peer, but very useful for multi-peer daemons like connectd and gossipd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-11-17 12:42:33 +01:00			`msgdata,status_io,peer,?node_id,`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgdata,status_io,who,wirestring,`
			`msgdata,status_io,len,u16,`
			`msgdata,status_io,data,u8,len`
status: generate messages rather than marshal/unmarshal manually. Now we have wirestring, this is much more natural. And with the 24M length limit, we needn't be so concerned about dumping 64k peer messages in hex. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-08 02:25:12 +01:00
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,status_fail,0xFFF2`
bolt-gen: use 'enum' instead of 'e:' prefix for enums use 'enum ' in wirespec instead of 'e:' as an indicator that a field is an enum. 2019-07-24 06:20:04 +02:00			`msgdata,status_fail,failreason,enum status_failreason,`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgdata,status_fail,desc,wirestring,`
status: separate types for peer failure vs "impossible" failures. Ideally we'd rename status_failed() to status_fatal(), but that's too much churn for now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-08 02:25:12 +01:00
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,status_peer_connection_lost,0xFFF3`
status: separate types for peer failure vs "impossible" failures. Ideally we'd rename status_failed() to status_fatal(), but that's too much churn for now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-08 02:25:12 +01:00
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,status_peer_billboard,0xFFF5`
			`msgdata,status_peer_billboard,perm,bool,`
			`msgdata,status_peer_billboard,happenings,wirestring,`
status: separate types for peer failure vs "impossible" failures. Ideally we'd rename status_failed() to status_fatal(), but that's too much churn for now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-08 02:25:12 +01:00			`# Note: 0xFFFF is reserved for MSG_PASS_FD!`