Report Premium polling timeouts in the quick start - #5
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 Premium transcript example could exhaust its polling loop without a result or error. It now raises a timeout and explains how to resume the same Premium read without requesting another purchase. API docs and OpenAPI remain the first discovery links.
Validation:
uv run python -m unittest discover -s tests -p test_transcription.py -vpassed all 12 tests. Executed the extracted README example through the real SDK with an HTTP mock transport for ready, pending then ready, failed, and 60 pending reads; all four passed. No production API calls or package release.