mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 18:11:28 +01:00
Code Issues Projects Releases Wiki Activity
e81d78ec4c
core-lightning/common/peer_failed.h

33 lines
921 B
C
Raw Normal View History

headers: fix up header idempotent lines. For future reference, done via: for f in `find wire/ bitcoin/ common/ lightningd -name '*.h' ! -name 'gen*'`; do ID=`echo -n LIGHTNING/$f | tr 'a-z' 'A-Z' | tr -cs 'A-Z0-9' _`; sed 's/^#\(ifndef\|define\) .*_H$/#\1 '$ID/ < $f | sed 's,#endif /..*_H ./$,#endif /* '$ID' */,' | bagto $f; done Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-08-28 18:06:01 +02:00
#ifndef LIGHTNING_COMMON_PEER_FAILED_H
#define LIGHTNING_COMMON_PEER_FAILED_H
lightningd/peer_failed: helper to send PKT_ERR and exit daemon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-02-24 06:52:55 +01:00
#include "config.h"
#include <ccan/compiler/compiler.h>
#include <ccan/short_types/short_types.h>
struct channel_id;
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
struct per_peer_state;
lightningd/peer_failed: helper to send PKT_ERR and exit daemon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-02-24 06:52:55 +01:00
/**
peer_failed: automatically hand PEER_FD, GOSSIP_FD; add gossip_index We make it a macro, since everyone uses PEER_FD and GOSSIP_FD constants (they're actually always the same, but this is slightly safer), and add a gossip_index arg: this is groundwork for when we want to hand the peer back to master for gossipd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-19 02:06:14 +01:00
* peer_failed - Exit with error for peer.
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
* @pps: the per-peer state.
lightningd/peer_failed: helper to send PKT_ERR and exit daemon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-02-24 06:52:55 +01:00
* @channel_id: channel with error, or NULL for all.
peer_failed: automatically hand PEER_FD, GOSSIP_FD; add gossip_index We make it a macro, since everyone uses PEER_FD and GOSSIP_FD constants (they're actually always the same, but this is slightly safer), and add a gossip_index arg: this is groundwork for when we want to hand the peer back to master for gossipd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-19 02:06:14 +01:00
* @fmt...: format as per status_failed(STATUS_FAIL_PEER_BAD)
lightningd/peer_failed: helper to send PKT_ERR and exit daemon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-02-24 06:52:55 +01:00
*/
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
void peer_failed(struct per_peer_state *pps,
const struct channel_id *channel_id,
const char *fmt, ...)
PRINTF_FMT(3,4) NORETURN;
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 02:06:15 +01:00
common/read_peer_msg: deconstruct into individual helper routines. The One Big API is confusing, and has enough corner cases that we should ditch it rather than add more. See: https://www.sandimetz.com/blog/2016/1/20/the-wrong-abstraction In particular, when openingd is changed to chat to peers even when it's not actively opening a channel, it wants to handle (most) errors by continuing, not calling peer_failed(). This exposes the constituent parts. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-08-02 08:49:55 +02:00
/* We're failing because peer sent us an error message: NULL
* channel_id means all channels. */
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
void peer_failed_received_errmsg(struct per_peer_state *pps,
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 02:06:15 +01:00
const char *desc,
channeld: treat all incoming errors as "soft", so we retry. We still close the channel if we *send* an error, but we seem to have hit another case where LND sends an error which seems transient, so this will make a best-effort attempt to preserve our channel in that case. Some test have to be modified, since they don't terminate as they did previously :( Changelog-Changed: quirks: We'll now reconnect and retry if we get an error on an established channel. This works around lnd sending error messages that may be non-fatal. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-12-13 11:16:14 +01:00
const struct channel_id *channel_id,
bool soft_error)
NORETURN;
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 02:06:15 +01:00
/* I/O error */
void peer_failed_connection_lost(void) NORETURN;
headers: fix up header idempotent lines. For future reference, done via: for f in `find wire/ bitcoin/ common/ lightningd -name '*.h' ! -name 'gen*'`; do ID=`echo -n LIGHTNING/$f | tr 'a-z' 'A-Z' | tr -cs 'A-Z0-9' _`; sed 's/^#\(ifndef\|define\) .*_H$/#\1 '$ID/ < $f | sed 's,#endif /..*_H ./$,#endif /* '$ID' */,' | bagto $f; done Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-08-28 18:06:01 +02:00
#endif /* LIGHTNING_COMMON_PEER_FAILED_H */
Reference in New Issue Copy Permalink