app-server thread/read can omit the live in-progress turn
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Root cause and proposed fix are prepared in the branch codex/thread-read-live-history of rc314159-creator/codex. The thread/read path reads persisted rollout history but does not merge ThreadState active_turn_snapshot(), unlike thread/turns/list. This can make the UI show a newer live user turn while a reader receives older history. The patch merges the active snapshot for legacy and paginated reads and adds a regression test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the app-server thread/read path and compare it with thread/turns/list, focusing on ThreadState active_turn_snapshot() and the existing rollout-history reads. The fix is expected to merge the active snapshot for both legacy and paginated reads; verify the regression test covers a live in-progress turn in each path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100