Repository navigation
Disable implicit SDK retries in consumer examples - #10
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.
The SDK examples omitted retry settings, although C3R v0.1 provides no request deduplication or idempotent replay guarantee. A timed-out generation could therefore be submitted again automatically.
Set Python
max_retries=0and JavaScriptmaxRetries:0, and document request-ID scope, ambiguous outcomes, explicit caller retry/reconciliation policy, incomplete responses and unmeasured cost. This changes only the developer guide; runtime, deployment and test trees are unchanged, and no new consumer adapter or production qualification is claimed.Validation: both existing official SDK HTTP/SSE acceptance fixtures passed (2 tests, 0 skips) after adding the existing Node installation to the test process PATH. The first JavaScript attempt failed to locate Node; no source fix was required. Standards and Spec reviews each reported zero actionable findings. No new tests were added for this documentation-only change.