-
Notifications
You must be signed in to change notification settings - Fork 38
feat: Phase 4 - EventPipeline integration with smart retry system #300
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
Merged
didiergarcia
merged 27 commits into
main
from
feat/tapi-retry-phase4-pipeline-integration
Apr 17, 2026
Merged
Changes from all commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
b96f558
feat(phase4): add retry infrastructure to EventPipeline
didiergarcia ce25d7f
test(phase4): add Step 1 verification tests
didiergarcia 4d66c96
feat(phase4): add upload gate to skip uploads when rate-limited
didiergarcia ca347d6
feat(phase4): add per-batch retry logic in upload loop
didiergarcia 8683777
feat: Phase 4 - EventPipeline integration with smart retry system
didiergarcia 68da12a
refactor: Rename EventPipelinePhase4Test to EventPipelineRetryInfrast…
didiergarcia 80dbe31
feat: Add timeProvider parameter to EventPipeline for testability
didiergarcia f6291ac
test: Add retry chain tests using FakeTimeProvider
didiergarcia c87da75
Merge branch 'main' into feat/tapi-retry-phase4-pipeline-integration
didiergarcia ec8132f
Fix SDK bugs found by e2e retry tests (#302)
MichaelGHSeg 19de1c6
fix: Reduce e2e-cli initial delay from 5s to 500ms
didiergarcia 4f78189
fix: Increase e2e-cli initial delay to 2s for settings error tolerance
didiergarcia eb8028c
fix: Use adaptive polling (1.5s initial + 200ms intervals) for e2e ti…
didiergarcia 6c5bfb3
fix: Remove fixed initial delay, use aggressive polling from start
didiergarcia da14a34
fix: Revert to 1.2s initial delay for SDK initialization
didiergarcia 9ef871b
fix: Reduce initial delay to 900ms to meet <1s timing requirement
didiergarcia fd7d1c6
fix: Use 2s HTTP timeouts for fast settings failure recovery
didiergarcia 998d230
fix: Track batch file lifecycle instead of assuming empty means done
MichaelGHSeg 3f42d7f
feat: read httpConfig from CDN settings and fix retry enforcement (#304)
MichaelGHSeg 3ee672c
test: Fix HttpConfigTest to use lowercase RetryBehavior values
didiergarcia de79472
fix: test isolation and timing flakiness (#305)
MichaelGHSeg d3ffcef
Adding more detailed logging to the tests to help with debugging test…
MichaelGHSeg 31fb465
Fix CI test failures by updating WaitingPlugin to use setup instead o…
MichaelGHSeg 788536b
fix: update waiting plugin test to use two manual resumes as automati…
MichaelGHSeg 391b2db
Setting test timeout to investigate hanging test
MichaelGHSeg fba8a2c
fix: address CI failures in WaitingTests and e2e 400 status test
MichaelGHSeg c5d8201
fix: use analyticsDispatcher for StartupQueue state subscription
MichaelGHSeg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it hurts anything, but I had asked Val about whether we should just always include it even when it's zero as a way to distinguish new non-retries from old retires-and-non-retries. Buuut if we're going to be moving to v2 anyway, that makes it entirely moot. The test will probably need to be changed to look for no retry count = 0 and I can fix the other SDKs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be consistent across the libraries. We can just always add it or do it only after the first one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's go with only after first attempt, so no x-retry-count=0. Neater, less traffic most of the time.