cln/lightningd/test
Christian Decker 57b9648d30 common: Resume the startup trace after exiting io_loop
This was a bit harder to identify: during an `io_loop` run we suspend
the current span before handing over to `io_loop`, and later when a callback
is called we resume the span again. Depending on how we return from
the `io_loop` instance that is used to drive the startup, we either
have resumed the last span, or we don't. Since we start a span before
`io_loop` and want it to be emitted afterwards, we need to take care
of the case where we returned from a callback that did not resume, and
therefore the current context is empty.

Making `trace_span_resume` idempotent means we can just resume it
manually.

Ideally we'd push the suspend / resume logic down into `io_loop`
itself, and then we'd have just one place. Maybe suspend and resume
callbacks that can be configured in `io_loop`?
2024-11-24 10:24:31 +10:30
..
Makefile lightningd/test/Makefile: add missing dependency on header_versions_gen.h 2024-11-23 13:03:00 +01:00
run-check_node_announcement.c common/msg_queue: send backtrace on oversize queues. 2024-11-01 16:54:49 +10:30
run-find_my_abspath.c common: Resume the startup trace after exiting io_loop 2024-11-24 10:24:31 +10:30
run-invoice-select-inchan.c close: Print multiple txs; Fixes #6467 2024-11-17 16:04:06 +10:30
run-jsonrpc.c common/msg_queue: send backtrace on oversize queues. 2024-11-01 16:54:49 +10:30
run-log-pruning.c common/msg_queue: send backtrace on oversize queues. 2024-11-01 16:54:49 +10:30
run-log_filter.c common/msg_queue: send backtrace on oversize queues. 2024-11-01 16:54:49 +10:30
run-shuffle_fds.c common/msg_queue: send backtrace on oversize queues. 2024-11-01 16:54:49 +10:30