Enforce single-writer ownership for paginated threads - #34986
Merged
copyberry[bot] merged 1 commit intoJul 23, 2026
Merged
Conversation
## Why Only one app-server process should keep a paginated thread open for writing at a time, while other processes must still be able to read it. ## What changed - Acquire a per-thread filesystem lock when creating or resuming a paginated thread, and retain it for the lifetime of the live recorder. - Reject a competing `thread/resume` request with JSON-RPC error `-32600` and release ownership when the writer is discarded, deleted, or shut down. - Remove stale lock files without disturbing active writers. ## Testing Added coverage for competing processes, ownership transfer after shutdown, stale-lock cleanup, and lock release during discard and deletion. GitOrigin-RevId: 81d49a2fffc73ba8135752b4944f27feafa4c0d6
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/81d49a2fffc73ba8135752b4944f27feafa4c0d6
branch
from
July 23, 2026 18:22
38ad864 to
5c94796
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/81d49a2fffc73ba8135752b4944f27feafa4c0d6
branch
July 23, 2026 18:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enforce single-writer ownership for paginated threads
Why
Only one app-server process should keep a paginated thread open for writing at
a time, while other processes must still be able to read it.
What changed
thread, and retain it for the lifetime of the live recorder.
thread/resumerequest with JSON-RPC error-32600andrelease ownership when the writer is discarded, deleted, or shut down.
Testing
Added coverage for competing processes, ownership transfer after shutdown,
stale-lock cleanup, and lock release during discard and deletion.