Repository navigation
fix(workspace): re-drive stuck transcript loads after rehydrate - #301
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
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
Tracking
Fixes #283.
Refs #290.
Why
Issue #283 showed that async initial-history loads can have their terminal ready/error write dropped when rehydrate or id churn rebuilds runtime keys mid-flight. Manual reload works because it re-runs the loader after ids settle. This PR automates that same recovery for durable provider sessions.
Scope note
This is a safety net, separate from the narrower fresh-JSONL tailer race fix in #298. It intentionally skips provisional proxy-header sessions; those are owned by the disconnected-transcript path from #293/#290.
Verification