Repository navigation
fix(providers): backport ChatGPT Web reasoning transport limits - #16145
Merged
Merged
Conversation
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
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.
ChatGPT Web reasoning preflights currently allow roughly one million inline characters. This backports the conservative 500,000-character ceiling adopted in upstream v6.1.7 (
f9ad4ae83a579287105ad822dd0c3e0029b04ef6) for Medium/High and Pro Extra High. A request at the ceiling remains accepted; the next character is rejected before browser dispatch with the existing non-retryablecontext_length_exceedederror. Multipart staging and final messages use the same policy.Instant, Pro mode, Luna/Think and token budgets retain their existing limits. The vendor pin remains v4.0.7; the comment records this hunk's upstream provenance. This is a partial behavioral backport for #14194, whose complete runtime refresh and required live ChatGPT smoke remain pending. The 500,000-character ceiling is an upstream safety margin, not a new measurement of the remote service's physical limit.
Validation:
7510677fand 17 PASS after the two-constant change. Failures were missing expected preflight rejections, with all existing-behavior controls passing.tests/unit/chatgpt-web-codex-transport-limits-14194.test.tsinvokes the real route resolution and single/multipart preflight functions, covering account/effort combinations, both sides of each boundary, independent token limits and unknown models.The existing worker/login work in #15935 and #15825 is preserved. This PR does not perform the complete v6.1.7 port or certify a live ChatGPT session. Hosted release CI and the broader #15306 tracking remain separate from these local results.
Refs #14194.