fix: unwanted long retry due to very long default config#1426
Merged
prakashsvmx merged 1 commit intominio:masterfrom Oct 14, 2025
aldy505:fix/unwanted-long-retry
Merged
fix: unwanted long retry due to very long default config#1426prakashsvmx merged 1 commit intominio:masterfrom aldy505:fix/unwanted-long-retry
prakashsvmx merged 1 commit intominio:masterfrom
aldy505:fix/unwanted-long-retry
Conversation
Fixes #1411 The previous retry implementation was not documented properly, which created unwanted behavior from this SDK. Hopefully the new defaults is acceptable and don't cause any performance bottlenecks.
Contributor
Author
|
@prakashsvmx @harshavardhana please review, thanks. |
Member
|
yes, 100ms default is fine and acceptable |
prakashsvmx
approved these changes
Sep 19, 2025
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.
Fixes #1411
The previous retry implementation was not documented properly, which created unwanted behavior from this SDK.
Hopefully the new defaults is acceptable and don't cause any performance bottlenecks.