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.
refactor: replace retry with internal async backoff retry loop #10663
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
base: main
Are you sure you want to change the base?
refactor: replace retry with internal async backoff retry loop #10663
Changes from all commits
289a888File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.
Check warning on line 18 in src/apiv2.ts
Check warning on line 18 in src/apiv2.ts
Check warning on line 19 in src/apiv2.ts
Check warning on line 19 in src/apiv2.ts
Check warning on line 136 in src/apiv2.ts
Check warning on line 241 in src/apiv2.ts
Check warning on line 280 in src/apiv2.ts
Check warning on line 281 in src/apiv2.ts
Check warning on line 281 in src/apiv2.ts
Check warning on line 281 in src/apiv2.ts
Check failure
Code scanning / CodeQL
Server-side request forgery Critical
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.
Avoid using
anyas an escape hatch per the TypeScript guidelines in the repository style guide. We should type the caught variable asunknownand use a safe conversion toErrorto ensure type safety.References
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.
When wrapping a generic caught error in a
FirebaseError, usingnew FirebaseError(${err})converts the error to a string (which includes the error name, e.g.,"Error: message") and discards the original stack trace.Instead, we should check if the caught error is an instance of
Errorand pass it as theoriginalproperty to preserve the stack trace and original error details.Uh oh!
There was an error while loading. Please reload this page.