[codex] Forward window.agent timeouts to remote dispatch#137
Open
xTRam1 wants to merge 2 commits into
Open
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
window.agent(timeout=...)into the remote-dispatch request body for bothnaradaandnarada-pyodide.Why
Python callers were timing out locally while the backend request still had the default long expiry. That let frontend child runnables keep running after the Python parent resumed, which could make retries hit the runnable stack invariant.
How I Tested This
Focused SDK tests:
Lint and diff checks:
Cross-repo live harness proof:
narada-pyodide==0.0.56.timeout-lifecycle-3283-fix4-20260529/tmp/narada-e2e-runs/20260529T214232Z-remotedispatchtimeoutlifecycle-timeout-lifecycle-3283-fix4-20260529Release note: after this SDK change is published, frontend should bump its configured
narada-pyodidedependency so product Pyodide workflows send the timeout without the harness shim.Codex sibling refs
codex/remote-dispatch-timeout-proof(no GitHub remote configured)