core-lightning/common/peer_status_wire.csv

#include <common/channel_id.h>
#include <common/per_peer_state.h>

# An error occurred: if error_for_them, that to go to them.
msgtype,status_peer_error,0xFFF4
# Do we force a disconnect from the peer?
msgdata,status_peer_error,disconnect,bool,
# The error string
msgdata,status_peer_error,desc,wirestring,
# Actually a warning, not a (fatal!) error.
msgdata,status_peer_error,warning,bool,
# The error to send to them in future if they try to talk to us about
# this channel.
msgdata,status_peer_error,len,u16,
msgdata,status_peer_error,error_for_them,u8,len
common/channel_id: move channel_id into its own file. The definition was in wire/wire.h, and helper functions in fromwire.c! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-05-15 19:59:53 +09:30			`#include <common/channel_id.h>`
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.`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-23 17:51:11 -05:00			`msgtype,status_peer_error,0xFFF4`
common: add peer_failed_warn_nodisconnect routine for non-disconnecting warnings We generalize the current df-only "aborted" flag (and invert it) to a "disconnected" flag in the peer status message. We convert it back to the aborted flag for now inside subd.c, but that's next. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-10-22 14:37:31 +10:30			`# Do we force a disconnect from the peer?`
			`msgdata,status_peer_error,disconnect,bool,`
			`# The error string`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-23 17:51:11 -05:00			`msgdata,status_peer_error,desc,wirestring,`
common: add peer_failed_warn_nodisconnect routine for non-disconnecting warnings We generalize the current df-only "aborted" flag (and invert it) to a "disconnected" flag in the peer status message. We convert it back to the aborted flag for now inside subd.c, but that's next. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-10-22 14:37:31 +10:30			`# Actually a warning, not a (fatal!) error.`
common: treat all "all-channels" errors as if they were warnings. This is in line with the warnings draft, where all-zeroes in a channel_id is no longer special (i.e. it will be ignored). But gossipd would send these if it got upset with us, so it's best practice to ignore them for now anyway. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: Protocol: we treat error messages from peer which refer to "all channels" as warnings, not errors. 2021-02-02 23:17:01 +10:30			`msgdata,status_peer_error,warning,bool,`
common: add peer_failed_warn_nodisconnect routine for non-disconnecting warnings We generalize the current df-only "aborted" flag (and invert it) to a "disconnected" flag in the peer status message. We convert it back to the aborted flag for now inside subd.c, but that's next. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-10-22 14:37:31 +10:30			`# The error to send to them in future if they try to talk to us about`
			`# this channel.`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-23 17:51:11 -05:00			`msgdata,status_peer_error,len,u16,`
			`msgdata,status_peer_error,error_for_them,u8,len`