History projection retries a duplicate ordinal forever
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
History projection retries a duplicate ordinal forever
Environment: Codex Desktop for Windows 26.901.51231, paginated thread history.
- Create a valid rollout whose projection cursor expects ordinal
N. - At that byte offset, place a second
thread_settings_appliedrecord with ordinalN-1, semantically identical to the immediately preceding record. - Open/resume the task repeatedly.
Expected: projection treats this exact duplicate as idempotent, advances past it, and continues at N.
Actual: every resume logs expected ordinal N, got N-1; the persisted cursor does not advance, so the same record is retried indefinitely. No rollout mutation is required to reproduce. Suggested fix: accept only an exact adjacent duplicate of an idempotent record type, advance the cursor transactionally, and retain fail-closed behavior for meaningful or compound records.
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
No file or test is named in the issue. Start by locating the history projection cursor handling and the ordinal-mismatch logging, then reproduce the paginated thread-history case described above. Done means an exact adjacent duplicate idempotent record advances the persisted cursor transactionally, while meaningful or compound records still fail closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100