Repository navigation
Read Session traces in the Console and show - #1053
Merged
Merged
Conversation
This was referenced Oct 22, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #987.
Evidence
showreportedBash: stale command; a trace-only live session lost its live status; Silent and heartbeat ignored log-record growth.After: the same focused regressions pass for Claude and Codex conversations, latest events, all three browser storage modes, Silent and heartbeat.
cargo test --test console: 46 passed;cargo test --test show_logs: 15 passed;cargo test --test run_health: 5 passed.npm test --prefix console: 46 passed, including append/reconnect/polling under old logs, dual recording and trace-only recording.cargo test --test show_logs show_keeps_the_latest_event_when_otlp_escaping_expands_a_record_past_64_kibfailed before the fix and passes afterward (80 KiB and 320 KiB encoded requests). The reviewer's exact reproduction also changed from failure to success.cargo fmt --checkandcargo clippy --all-targets -- -D warningspass on the final commit.testpassed on final headd5349ba./usr/bin/time -p scripts/affected-tests d56453d5541b879cd04a4f202aa2937dc14ba3d6selectedcargo nextest run. Perdocs/testing.md, stopped this duplicate after exact-head CI passed: 996.11 seconds elapsed including compilation, 396 tests passed before cancellation, 4 interrupted, 3 skipped. This was an interrupted run, not a completed local full-suite result.Test seams
show/show --jsonandstatus --jsonCLI observations.Review
Independent Standards and Spec reviews use the fetched
issue-700fixed point,d56453d5541b879cd04a4f202aa2937dc14ba3d6.Standards: 0 findings. Spec: 1 P2 finding, reproduced and fixed by reading a complete OTLP request across the tail window; regression retained. Both reviewers checked the final fix.
Changed files left unread: none under either axis (15/15 files read by each reviewer). Generated-output exclusions: none.
Unaddressed findings
Standards
None.
Spec
None. The large-record latest-event finding was addressed.
Merge Danger
Door: two-way
Reader changes can be reverted; retained Session logs and Session traces stay intact.
Blast Radius: readers
Console log inventory, conversations and streams; latest live events in
show; Silent and heartbeat observations.Built with codex · gpt-6.1-sol · xhigh