node/reactor: Rewrite `Runtime::run` and introduce `LAG_TIMEOUT`
Since the service performs further I/O (e.g. uses SQLite), it can keep the reactor runtime thread busy for long periods. Emit a warning if that is the case.
100 ms is quite relaxed, this is to only catch severe cases and avoid spamming the log.
Since the service performs further I/O (e.g. uses SQLite), it can keep the reactor runtime thread busy for long periods. Emit a warning if that is the case.
100 ms is quite relaxed, this is to only catch severe cases and avoid spamming the log.
Rebase