core-lightning/common/status_wire.csv

#include <common/status_wire.h>

status_log,0xFFF0
status_log,,level,enum log_level
status_log,,entry,wirestring

status_io,0xFFF1
status_io,,iodir,enum log_level
status_io,,len,u16
status_io,,data,len*u8

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

status_peer_connection_lost,0xFFF3

# Note: 0xFFFF is reserved for MSG_PASS_FD!
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>`

			`status_log,0xFFF0`
			`status_log,,level,enum log_level`
			`status_log,,entry,wirestring`

			`status_io,0xFFF1`
			`status_io,,iodir,enum log_level`
			`status_io,,len,u16`
			`status_io,,data,len*u8`

			`status_fail,0xFFF2`
			`status_fail,,failreason,enum status_failreason`
			`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
			`status_peer_connection_lost,0xFFF3`

			`# Note: 0xFFFF is reserved for MSG_PASS_FD!`