Skip to content

Avoid nested read locking when rendering browser sign-in - #47861

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/ba83e212d510627be9dfd068c8d7318da32a1749
Sep 24, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/ba83e212d510627be9dfd068c8d7318da32a1749

Conversation

@copyberry

@copyberry copyberry Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Avoid nested read locking when rendering browser sign-in

Why

render_ref already holds a read lock on sign_in_state. Acquiring another read lock in render_continue_in_browser can deadlock when a writer is waiting.

What changed

Pass the borrowed ContinueInBrowserState from render_ref into the browser sign-in renderer instead of reading the lock again.

Testing

Update the existing narrow-width browser sign-in test to exercise render_ref, retaining checks for the full OSC 8 authentication link, device-code guidance, and cancellation footer.

## Why

`render_ref` already holds a read lock on `sign_in_state`. Acquiring another read lock in `render_continue_in_browser` can deadlock when a writer is waiting.

## What changed

Pass the borrowed `ContinueInBrowserState` from `render_ref` into the browser sign-in renderer instead of reading the lock again.

## Testing

Update the existing narrow-width browser sign-in test to exercise `render_ref`, retaining checks for the full OSC 8 authentication link, device-code guidance, and cancellation footer.

GitOrigin-RevId: ba83e212d510627be9dfd068c8d7318da32a1749
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/ba83e212d510627be9dfd068c8d7318da32a1749 branch from 35e5446 to 3e9d1d2 Compare September 24, 2026 15:21
@copyberry
copyberry Bot merged commit 3e9d1d2 into main Sep 24, 2026
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/ba83e212d510627be9dfd068c8d7318da32a1749 branch September 24, 2026 15:21
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 24, 2026
@gysi
gysi deployed to issue-triage September 24, 2026 15:25 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:25 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:25 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:26 — with GitHub Actions Active
@donenkodv
donenkodv deployed to issue-triage September 24, 2026 15:32 — with GitHub Actions Active
@donenkodv
donenkodv deployed to issue-triage September 24, 2026 15:32 — with GitHub Actions Active
@donenkodv
donenkodv deployed to issue-triage September 24, 2026 15:32 — with GitHub Actions Active
@donenkodv
donenkodv deployed to issue-triage September 24, 2026 15:33 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:41 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:41 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:41 — with GitHub Actions Active
@gysi
gysi deployed to issue-triage September 24, 2026 15:42 — with GitHub Actions Active
@pbamp
pbamp deployed to issue-triage September 24, 2026 15:50 — with GitHub Actions Active
@pbamp
pbamp deployed to issue-triage September 24, 2026 15:50 — with GitHub Actions Active
@pbamp
pbamp deployed to issue-triage September 24, 2026 15:50 — with GitHub Actions Active
@pbamp
pbamp deployed to issue-triage September 24, 2026 15:52 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
issue-triage — 3e9d1d29 Deployed Sep 24, 2026 by pbamp via Identify potential duplicates (open issues fallback) #48026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants