Repository navigation
fix(strategy27): retain display history across stream epochs - #279
Merged
Merged
Conversation
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
1 participant
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.
A live
stream_stateresponse withtransport_recoveredcleared all ordinary Strategy 27 arrows and panel history even though the chart context stayed unchanged. CDP captured the loaded 0.4.3 script entering that clear branch with two markers and eight panel rows; ordinary close messages had retained the markers.Keep protocol epoch/cursor validation separate from ordinary display ownership. Retain verified arrows and merge bootstrap/event replay by event ID, preserving the original directional marker. Bound display history independently to 80 events and two hours, mark pre-reset panel records as historical until updated, and preserve manual/context cleanup. Publish generated version 0.4.4.
Validation: source/generated integration regressions reproduce the original deletion and verify retention, replay, stale-cursor recovery, capacity, age, and context/manual cleanup. Panel DOM and standalone rendered-browser checks cover historical state, selection, compound isolation, and collapse/restore. Strategy 27 tests, full repository tests, generated build, syntax checks, release contract, and diff checks pass. Live post-release verification is tracked separately from these local checks.