Repository navigation
修正 Codex STATE 续接并对齐 ranxi v2.10.5 借用验证 - #282
Merged
Merged
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.
Codex HTTP continuation discarded client STATE whenever process-local provenance was absent or expired. This restores ranxi v2.10.5's behavior: preserve unknown state and strip only a live foreign-account state, while keeping the independent two-shot borrowing qualification unchanged.
d977e7a5e24e5536db6ce8b8478743e0c4b11f77; execute extracted original functions in differential tests for source payload, target wire/verdict, cookie lifetime and business STATE. Sol remains separately qualified.Validation: extracted-reference provenance check; differential protocol tests; known/unknown/expired STATE tests; pre-HTTP retry tests; native replay isolation and forwarding tests; keepalive completion/cancellation tests. Only the locally failed parser-wording fixture was rerun after adaptation. The new keepalive race check runs in normal PR CI.
Production model-quality acceptance is pending deployment and is not implied by these offline results. No database migration, BPS/WS activation or recurring update automation is included.