Repository navigation
Fix Responses trace capture and prepare 0.1.0 release - #2
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.
Responses API failures returned as HTTP 200 responses were treated as successful calls, and stopping a Responses stream before its final event discarded received tool calls and text. Capture those failures without changing SDK behavior, preserve partial streamed output, and add six regression cases covering failure, recovery and interrupted streams.
Prepare the standalone trace-based pytest package as 0.1.0 alpha. Run the full suite on Python 3.11–3.13 in CI and before tagged publishing, validate the installed wheel, correct the tested SDK versions, and include examples and test helpers in the source distribution.
Validation: 195 tests pass locally on Python 3.13, both from source and against the installed wheel; strict distribution metadata and dependency checks pass. The first PyPI upload remains dependent on fixing the trusted publisher configuration (the prior v0.0.0 attempt failed with invalid-publisher).