Repository navigation
feat(observability): expose scoped construction operation timings - #1259
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The ordinary host construction receipts recorded whole-ingest wall time but omitted the append, seal and resumed-construction durations required by #901. Import validation and commit now expose per-invocation wall-time observations for construction begin, resume, append, seal and publication, with attempted-call and error counts.
Timing state resets before each operation, records returned errors and stays out of durable manifests. Successful CLI receipts expose the closed numeric object; the existing certifier preserves it and rejects malformed counters or extra fields. Documentation distinguishes these scopes from durable phase I/O, CPU and whole-ingest time, including work that failed commands or lost processes cannot report.
Direct regressions cover repeated validation, persisted manifests, cancelled publication and successful retry with an immediate same-facade relationship query, plus separate-process CLI validate/commit/status receipts. The existing tiny/growth lifecycle also asserts that actual CLI receipts retain the expected timings through the certifier. The new accessor is included in the public method inventory with its direct regression and explicitly classified as a Rust/CLI diagnostic in Python and Node parity inventories.
Validation:
make pre-pushstopped only at existing test(storage): respect native TMPDIR in socket inventory regression #1192: the hardcoded-/tmpsocket fixture receivesGF_UNSUPPORTED_FILESYSTEM(storage 1,097 passed, 1 failed, 2 existing ignored). Later local stages were not reached; no full local gate pass is claimed.Closes #1256.