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 ef80b84
Browse filesBrowse the repository at this point in the historyBrowse files
fix(client-runtime): queued runs that start after a steer show up in the thread
A queued run keeps the run ordinal it got when it was queued, and the server
bands its turn items by that ordinal. A steer or new turn sent later gets a
higher ordinal and runs first, and on a partially loaded thread its items
raise the client's latestLocalTurnOrdinal watermark. When the queued run
finally started, every one of its items sat below the watermark, so the
partial-timeline guard treated them as unloaded history and dropped them.
The resume cursor still moved past those events and the thread cache kept
the gap, so reloading did not bring them back.
The guard now keeps a missing item when its run is still queued in the
client's projection (the orchestrator commits a queued run's first item
before the run.updated that starts it), and when the window already shows
an earlier item of the same run (which also covers #16437's case). Items
of other runs below the window are still dropped.
Thread cache entries now carry their own schema version (4), so web and
mobile discard thread snapshots saved with the gap and fetch a fresh
bounded snapshot. Shell caches keep version 3 and stay warm.
Fixes#16987
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments