You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c420e9e
Browse filesBrowse the repository at this point in the historyBrowse files
Address review feedback on HTTP thread snapshot loading
- ws.ts (afterSequence resume): attach the live PubSub subscription into a
scope-bound buffer BEFORE draining the catch-up replay, so events published
during the replay window are not lost; read the full range after the cursor
(readEvents limit) so the per-thread filter can't be starved by a global cap.
- ProjectionSnapshotQuery: add getThreadDetailSnapshot that reads thread detail
+ snapshot sequence in one transaction, so the sequence is consistent with the
returned state; use it in the HTTP handler and the WS snapshot path.
- OrchestrationEngine.readEvents: accept an optional limit.
- client loader: bound the HTTP snapshot timeout (cached data renders meanwhile)
and treat a 404 as an expected defer-to-socket case rather than a warning.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
0 commit comments