lukechilds
/
lightning
mirror of https://github.com/lukechilds/lightning.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3722 Commits
55 Branches
107 Tags
38 MiB
Tree: 6231e9969f
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6231e9969f'
${ noResults }
lightning/common/status.h

54 lines
1.6 KiB
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>
7 years ago
#ifndef LIGHTNING_COMMON_STATUS_H
#define LIGHTNING_COMMON_STATUS_H
status: API for status reporting. The API formalizes how daemons should report their statuses back to the main lightningd. It's a simple write API, which includes tracing support (currently it always sends traces, later it could send iff there's a failure, for example). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
8 years ago
#include "config.h"
#include <ccan/compiler/compiler.h>
#include <ccan/short_types/short_types.h>
status: split off error messages into a new &#39;peer_status&#39; type. Several daemons (onchaind, hsm) want to use the status messages, but don&#39;t communicate with peers. The coming changes made them drag in more code they didn&#39;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 &#39;error_for_them&#39; field indicating direction. We also rename status_fatal_connection_lost() to peer_failed_connection_lost() to fit in. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#include <ccan/take/take.h>
status: add multiple levels of logging. status_trace maps to status_debug. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#include <common/status_levels.h>
common/status: add status_tracev() for making status wrappers. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#include <stdarg.h>
status: add multiple levels of logging. status_trace maps to status_debug. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#include <stdbool.h>
status: API for status reporting. The API formalizes how daemons should report their statuses back to the main lightningd. It&#39;s a simple write API, which includes tracing support (currently it always sends traces, later it could send iff there&#39;s a failure, for example). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
8 years ago
#include <stdlib.h>
status: separate types for peer failure vs &#34;impossible&#34; failures. Ideally we&#39;d rename status_failed() to status_fatal(), but that&#39;s too much churn for now. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
struct channel_id;
lightningd/status: support daemon_conn for status_trace and status_failed. We remove the unused status_send_fd, and rename status_send_sync (it should only be used for that case now). We add a status_setup_async(), and wire things internally to use that if it&#39;s set up: status_setup() is renamed status_setup_sync(). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
8 years ago
struct daemon_conn;
status: API for status reporting. The API formalizes how daemons should report their statuses back to the main lightningd. It&#39;s a simple write API, which includes tracing support (currently it always sends traces, later it could send iff there&#39;s a failure, for example). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
8 years ago
/* Simple status reporting API. */
lightningd/status: support daemon_conn for status_trace and status_failed. We remove the unused status_send_fd, and rename status_send_sync (it should only be used for that case now). We add a status_setup_async(), and wire things internally to use that if it&#39;s set up: status_setup() is renamed status_setup_sync(). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
8 years ago
void status_setup_sync(int fd);
void status_setup_async(struct daemon_conn *master);
status: API for status reporting. The API formalizes how daemons should report their statuses back to the main lightningd. It&#39;s a simple write API, which includes tracing support (currently it always sends traces, later it could send iff there&#39;s a failure, for example). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
8 years ago
status: add multiple levels of logging. status_trace maps to status_debug. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
/* Send a printf-style debugging trace. */
void status_fmt(enum log_level level, const char *fmt, ...)
PRINTF_FMT(2,3);
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
status: add multiple levels of logging. status_trace maps to status_debug. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
/* vprintf-style */
void status_vfmt(enum log_level level, const char *fmt, va_list ap);
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
common: only log io if they set --debug-subdaemon-io=&lt;daemon&gt; or with SIGUSR1. Otherwise we just log the type of msg. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
/* Usually we only log the packet names, not contents. */
extern volatile bool logging_io;
log: separate levels for IO directions, allow msg + io data. We currently don&#39;t handle LOG_IO properly, and we turn it into a string before handing it to the -&gt;print function, which makes it ugly for the case where we&#39;re using copy_to_parent_log, and also means in that case we lose *what peer* the IO is coming from. Now, we handle the io as a separate arg, which is much neater. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
void status_io(enum log_level iodir, const u8 *p);
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
status: add multiple levels of logging. status_trace maps to status_debug. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
/* Helpers */
#define status_debug(...) \
status_fmt(LOG_DBG, __VA_ARGS__)
#define status_info(...) \
status_fmt(LOG_INFORM, __VA_ARGS__)
#define status_unusual(...) \
status_fmt(LOG_UNUSUAL, __VA_ARGS__)
#define status_broken( ...) \
status_fmt(LOG_BROKEN, __VA_ARGS__)
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
status: add multiple levels of logging. status_trace maps to status_debug. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
/* FIXME: Transition */
#define status_trace(...) status_debug(__VA_ARGS__)
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
status: API for status reporting. The API formalizes how daemons should report their statuses back to the main lightningd. It&#39;s a simple write API, which includes tracing support (currently it always sends traces, later it could send iff there&#39;s a failure, for example). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
8 years ago
/* Send a failure status code with printf-style msg, and exit. */
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&#39;t be so concerned about dumping 64k peer messages in hex. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
void status_failed(enum status_failreason code,
const char *fmt, ...) PRINTF_FMT(2,3) NORETURN;
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
status: separate types for peer failure vs &#34;impossible&#34; failures. Ideally we&#39;d rename status_failed() to status_fatal(), but that&#39;s too much churn for now. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
/* Helper for master failures: sends STATUS_FATAL_MASTER_IO.
status: use common status codes for all the failures. This change is really to allow us to have a --dev-fail-on-subdaemon-fail option so we can handle failures from subdaemons generically. It also neatens handling so we can have an explicit callback for &#34;peer did something wrong&#34; (which matters if we want to close the channel in that case). Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
* msg NULL == read failure. */
status: separate types for peer failure vs &#34;impossible&#34; failures. Ideally we&#39;d rename status_failed() to status_fatal(), but that&#39;s too much churn for now. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
void master_badmsg(u32 type_expected, const u8 *msg) NORETURN;
common: peer_billboard() helper for updating the billboard. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
void status_send(const u8 *msg TAKES);
peer_failed: hand fds back to master when we fail. master now hands it back to gossipd. Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
void status_send_fatal(const u8 *msg TAKES, int fd1, int fd2) NORETURN;
headers: fix up header idempotent lines. For future reference, done via: for f in `find wire/ bitcoin/ common/ lightningd -name &#39;*.h&#39; ! -name &#39;gen*&#39;`; do ID=`echo -n LIGHTNING/$f | tr &#39;a-z&#39; &#39;A-Z&#39; | tr -cs &#39;A-Z0-9&#39; _`; sed &#39;s/^#\(ifndef\|define\) .*_H$/#\1 &#39;$ID/ &lt; $f | sed &#39;s,#endif /..*_H ./$,#endif /* &#39;$ID&#39; */,&#39; | bagto $f; done Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
7 years ago
#endif /* LIGHTNING_COMMON_STATUS_H */