fix(server): retain events while opening a thread - #273
Merged
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
(cherry picked from commit 9c9ae3dc0e94a957d9c4a61bb211caf914828054)
rynfar
force-pushed
the
upstream/2026-09-05-thread-subscription
branch
from
September 6, 2026 02:32
22f3642 to
9f6b117
Compare
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.
Opening a thread can miss events published while its initial snapshot loads, making a running agent appear stalled. Start the live subscription consumer immediately, before reading the snapshot.
Adopts upstream #9521 (
9c9ae3dc0e). Applies to every provider and client connection mode without changing Pylon's admission or Prime recovery logic. Records the partial adoption in the upstream ledger.Validation: all 154 server-router tests, server typecheck, formatting and targeted lint pass. The regression fails with the original startup and passes with the fix; it waits on the synchronization marker instead of a sleep.
CI exposed a Pylon legacy-client fixture that assumed the old subscription scheduling. Its live events now wait for the client synchronization receipt, preserving the rollback-filter assertion without timing assumptions.
The durable implementation and review record is consolidated in companion #279.
Model: GPT-6 Astra. Harness: Codex.