-
Notifications
You must be signed in to change notification settings - Fork 97
Response status updates #531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
MichaelGHSeg
wants to merge
22
commits into
master
Choose a base branch
from
response-status-updates
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+335
−46
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
…java into release/3.5.4
* Changing release plugin * Deploy working * Rolling back to snapshot * [maven-release-plugin] prepare release analytics-parent-3.5.4 * [maven-release-plugin] prepare for next development iteration * putting back release instructions
…java into release/3.5.4
…to response-status-updates
- Add Authorization header with Basic auth to all requests - Reduce retry backoff times for faster recovery (100ms base, 1min cap) - Respect Retry-After header with 5-minute max cap - Always include X-Retry-Count header in requests - Consolidate SegmentService upload methods - Increase max flush attempts to accommodate shorter backoff times Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove 413 (Payload Too Large) from retryable status codes Payload size won't shrink on retry, so retrying is pointless - Verify 503 Retry-After handling matches spec 503 checks Retry-After header first, falls back to exponential backoff - Add test for 413 non-retryable behavior - Add test for Retry-After delay mechanism (validates cap logic) The 300-second cap is enforced at AnalyticsClient.java:556-558 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
No description provided.