Repository navigation
fix: open bugs 429, 435, 436, 439 and cut v1.3.171 - #448
Merged
Merged
Conversation
A gateway 429 such as fable_requires_max carries no upstream quota headers. ingestHeaders was marking the 5h window rejected from the status alone. #439
Already-committed hops and responses that have been written downstream still stop on that slot. #435
A stream now sends a ping before the first token and commits that attempt, so a reverse proxy does not time out at 120s. The panel setting failover.max_request_mib caps both the gateway and the slot kernels. A Codex kernel recycles only when its slot is otherwise idle, after the old process has exited. #429 #436
A recycle deadline is not an exit. SIGTERM, then SIGKILL, and drop the socket only after the process is gone. If it is still alive, keep the tracked child and fail the recycle instead of spawning another kernel.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: 318189e7-4517-421c-a58e-c85fa4f781bd) |
This was referenced Oct 15, 2026
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
1 participant
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
fable_requires_max）不再把 5h 标成 rejected；真实上游额度拒绝仍生效。server_error换槽；已提交的不换。Test plan
account-quota、codex-slot-pool、handle-codex、stream-keepalive、routing-file、kernel-router、routing-runtime-load、codex-kernel-client相关单测Note
Medium Risk
Changes affect quota gating, streaming commit/failover timing, Codex slot switching, and ingress/kernel body limits with idle kernel restarts—operational but not auth/data-migration critical.
Overview
v1.3.171 tightens quota accounting, streaming reliability, Codex failover, and configurable request body limits.
Quota (#439):
ingestHeadersno longer treats every HTTP 429 as exhausted. Local limits (e.g.fable_requires_maxwithexhausted: falseand no rejected quota headers) leave the 5h window allowed; real upstream rejection still uses rejected headers orexhausted: true.Streaming (#429): Downstream keepalive is armed before the first upstream byte. After the interval, the gateway can send 200 + SSE ping, which commits the attempt so a later upstream failure cannot switch slots on that socket. Failures before the ping can still failover.
Codex (#435): Uncommitted upstream 503 with
server_erroris treated as transient failover; committed hops or responses already written to the client are not retried on another slot.Request body limit (#436): Settings → pool → failover adds 「请求体上限」 (
failover.max_request_mib, 8–128 MiB, default 32).inboundBodyLimitcaps gateway ingress (≤KIN_MAX_BODY);maxRequestBytesflows into Claude/Codex kernel configs. Saving routing patches syncs kernel config and reloads Claude kernels when idle; Codex kernels recycle only when the slot has ≤1 in-flight request and the old process has exited (socket removed after exit).Docs/API and the pool settings UI reflect the new limit behavior.
Reviewed by Cursor Bugbot for commit dcb2b4b. Configure here.