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 29677d1
Browse filesBrowse the repository at this point in the historyBrowse files
Fix thread subscription event loss and snapshot sequence race
- Attach the domain-event PubSub subscription before reading the
catch-up replay or snapshot baseline in subscribeThread, so events
published while the baseline loads are buffered instead of dropped
(new OrchestrationEngine.subscribeDomainEvents, scoped to the RPC
stream's lifetime via observeRpcStreamEffect).
- Make the afterSequence catch-up replay exhaustive instead of
truncating at the event store's default 1,000-event cap, which could
silently drop thread events under multi-thread activity.
- Read the thread detail and projection snapshot sequence inside one
transaction (ProjectionSnapshotQuery.getThreadDetailSnapshot), shared
by the HTTP threadSnapshot endpoint and the WS snapshot path, so the
reported sequence can never run ahead of the embedded thread.
0 commit comments