Repository navigation
Add sixteen sdkharness resilience checks: retry, backoff, reauthorization - #221
Merged
Merged
Conversation
sophiecarreras
force-pushed
the
sdkharness/resilience-slice-1
branch
from
October 14, 2026 16:49
4e45f33 to
11d6780
Compare
sophiecarreras
changed the base branch from
master
to
sdkharness/conformance-slice-1
October 14, 2026 16:49
…tion Adds the resilience level to the .sdkharness/ contract: one scenario per run, named by SDKHARNESS_SCENARIO, run by tests/run-resilience. Each check is a Java program that arms one documented fault through the simulator's control listener, makes one SDK call with the SDK's own default retry policy, and asserts the end state (bytes read back, listing, or the error) and the recovery path from the simulator's request journal: a fresh upload URL after a 503, 500, 408, 401, reset or stall, no retry after a 403 cap_exceeded, reauthorization after a 401 and after the token's 24 h life, and the lower bound of a Retry-After or the first backoff step. The stall check sets a 2 s socket timeout through the documented HttpClientFactoryImpl.Builder.setSocketTimeoutSeconds. A check still running after 60 s is killed and reported as a failure. The harness builds the core and httpclient jars and passes them as SDKHARNESS_JAVA_CLASSPATH; the build is unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…p errors, enforce loopback at request time, anchor the verdict match - A bucket or file the check could not delete, or faults it could not clear, now fails the verdict; every step is still attempted and the single result line is still printed. - Every check builds its client from one guarded HTTP client factory (the SDK's request settings, including the per-check socket timeout) that refuses any request whose target host is not 127.0.0.1 and fails the verdict if one was attempted. The control-listener requests are held to the same host. GuardSelfTest proves it. - run-resilience matches the result line at column 1 with index(), not anywhere in a line. - README: say what is guaranteed (formatting and capping, not redaction). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
sophiecarreras
force-pushed
the
sdkharness/resilience-slice-1
branch
from
October 14, 2026 17:59
11d6780 to
555a8eb
Compare
sophiecarreras
marked this pull request as ready for review
October 14, 2026 18:00
ffumero2003
approved these changes
Oct 14, 2026
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
2 participants
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.
Draft: this branches off master, not off #220, and both change
.sdkharness/tests.tsvand.sdkharness/README.md. I will rebase it once #220 merges, so please review #220 first.Adds the resilience level to the
.sdkharness/contract: one scenario per run, named bySDKHARNESS_SCENARIO, run bytests/run-resilience. Each check is a Java program that arms one documented fault through the simulator's control listener, makes one SDK call with the SDK's default retry policy, and asserts the end state and the recovery path from the simulator's request journal.upload.stallsets a 2 s socket timeout throughHttpClientFactoryImpl.Builder.setSocketTimeoutSeconds.Results against the pinned simulator: 16 of 16 pass on a JDK 17 launcher and on a JDK 11 launcher (
javac --release 11), three runs each, no flakiness.🤖 Generated with Claude Code