feat(core): integrate RetryManager into SegmentDestination upload pipeline#1160
Open
abueide wants to merge 1 commit intotapi/retry-manager-testsfrom
Open
feat(core): integrate RetryManager into SegmentDestination upload pipeline#1160abueide wants to merge 1 commit intotapi/retry-manager-testsfrom
abueide wants to merge 1 commit intotapi/retry-manager-testsfrom
Conversation
…eline Wire RetryManager into SegmentDestination for TAPI-compliant retry handling: uploadBatch() with error classification, event pruning on partial failures, retry count header propagation, and QueueFlushingPlugin error type handling updates. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
RetryManagerintoSegmentDestinationfor TAPI-compliant retry handlinguploadBatch()method with error classification, retry-after parsing, and configurable retry behaviorX-Retry-Count) propagation to API requestsQueueFlushingPluginerror type handling for retry vs permanent errorsPR 5 of 5 in the TAPI backoff/retry stack. Depends on #1159.
Test plan
npx jest --testPathPattern="SegmentDestination|QueueFlushingPlugin|api.test"— 42 tests passnpx tsc --noEmit— no type errorsnpx eslint— 0 errors🤖 Generated with Claude Code