Start-up is not traced #374
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found reviewing what production's traces and metrics leave out, 2026-10-25. Opening the database, creating what is missing and the catalogue's repairs (retire_stranded, regroup_unmanaged) run before the daemon serves and have no trace, so how long a deploy took to come back, and what held it, are unknown. Wanted: a start-up trace with a span each.
Fixed in
dd91602: a start trace from open_database and assemble_config through the repairs to daemon started; production's first was 347 ms. Deployed 2026-10-25.