Fix cross-process model cache reuse - #114
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
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.
The SDK represents input/output modalities as sets. Their JSON list order varied between Python processes, so identical CLI runs could miss cached model results. Canonicalize those lists and look up the bounded legacy order variants to preserve existing paid results.
Also expose nested JSON Schema failure locations to bounded repair prompts without printing rejected values. Regression tests verify stable keys, legacy reads and unchanged caller data; the workflow tests, lint and changed-file type checks pass. Prepare patch version 0.4.19.