core-lightning/common/peer_status_wire.csv

#include <common/per_peer_state.h>

# An error occurred: if error_for_them, that to go to them.
status_peer_error,0xFFF4
# This is implied if error_for_them, but master tries not to parse packets.
status_peer_error,,channel,struct channel_id
status_peer_error,,desc,wirestring
status_peer_error,,pps,struct per_peer_state
status_peer_error,,len,u16
status_peer_error,,error_for_them,len*u8
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-04 03:41:25 +09:30			`#include <common/per_peer_state.h>`
status: split off error messages into a new 'peer_status' type. Several daemons (onchaind, hsm) want to use the status messages, but don't communicate with peers. The coming changes made them drag in more code they didn't need, so instead we have a different non-overlapping type. We combine the status_received_errmsg and status_sent_errmsg into a single status_peer_error, with the presence or not of the 'error_for_them' field indicating direction. We also rename status_fatal_connection_lost() to peer_failed_connection_lost() to fit in. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-19 11:36:15 +10:30
			`# An error occurred: if error_for_them, that to go to them.`
			`status_peer_error,0xFFF4`
			`# This is implied if error_for_them, but master tries not to parse packets.`
			`status_peer_error,,channel,struct channel_id`
			`status_peer_error,,desc,wirestring`
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-04 03:41:25 +09:30			`status_peer_error,,pps,struct per_peer_state`
status: split off error messages into a new 'peer_status' type. Several daemons (onchaind, hsm) want to use the status messages, but don't communicate with peers. The coming changes made them drag in more code they didn't need, so instead we have a different non-overlapping type. We combine the status_received_errmsg and status_sent_errmsg into a single status_peer_error, with the presence or not of the 'error_for_them' field indicating direction. We also rename status_fatal_connection_lost() to peer_failed_connection_lost() to fit in. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-02-19 11:36:15 +10:30			`status_peer_error,,len,u16`
			`status_peer_error,,error_for_them,len*u8`