Skip to content

Expose recovery signal loss categories - #782

Draft
beinan wants to merge 1 commit into
mainfrom
codex/recovery-signal-loss-diagnostics-48049
Draft

beinan wants to merge 1 commit into
mainfrom
codex/recovery-signal-loss-diagnostics-48049

Conversation

@beinan

@beinan beinan commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

A dropped ordinary activity hint currently makes the recovery feed incomplete for five minutes, but operators cannot distinguish it from a dropped read-error or slow-read hint. Add a bounded loss object with separate cumulative counters and recent-loss flags, plus per-snapshot skipped-shard, truncated-row, and concurrent-recording-loss diagnostics.

The existing complete field and its conservative coverage rules remain unchanged. The new independently sampled counters describe lost hints, not failed user requests or critical-only coverage. This changes only the recovery-signal module and its documentation; no deployment or rollout gate is changed.

Validation: cargo test -p lance-context-metrics --all-targets --locked (17 unit tests plus HTTP middleware integration test passed; manual throughput benchmark ignored), package formatting, and cargo clippy -p lance-context-metrics --all-targets --locked -- -D warnings. Regression coverage distinguishes ordinary-only loss with a preserved503, actual critical loss, slow404 classification, independently expiring loss windows, and response truncation.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant