fix(proxy): integrate transport reliability fixes - #1
Merged
Conversation
Keep the one-second generic task cancellation bound while allowing normal direct Responses WebSocket scope finalization to use a bounded five-second observation window. Preserve the shared shutdown deadline and add a regression plus OpenSpec contract. Refs Soju06#1711
kevinsslin
marked this pull request as ready for review
August 14, 2026 05:20
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
Integrates the three transport-reliability fixes we are maintaining for the production fork on top of the current upstream
main:2164b8c0to upstreamc3f0c568;cleanup_phaseobservability from feat(proxy): report websocket cleanup phase Soju06/codex-lb#1726;This PR is the deployment integration branch for
kevinsslin/codex-lb. The upstream PRs remain open for independent maintainer review.Why
The live v1.23.0 VPS continued to show
missing_response_created_timeout,upstream_request_timeout, cleanup budget warnings, repeated 503 cooldown responses, and Codex tasks pausing after reconnect exhaustion. The official fixes are not yet merged into an upstream release.Safety
codex-lb==1.23.0rollback path.Validation
822 passed;uv run ruff check app tests;uv run ruff format --check app tests— 896 files formatted;uv run ty check;uv run python scripts/check_proxy_architecture.py;--strict;57 passed, 0 failed;git diff --check upstream/main...HEAD.Deployment
After merge, the VPS will install this fork's exact merged
mainSHA rather than the moving branch name, restartcodex-lb, and run health plus bounded transport/log canaries.