-
Notifications
You must be signed in to change notification settings - Fork 149
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
fix: Don't re-open streams on 'error' and 'end' #713
Conversation
c0c9d1b
to
6ff2756
Compare
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.
LGTM
Codecov Report
@@ Coverage Diff @@
## master #713 +/- ##
==========================================
- Coverage 96.21% 96.05% -0.17%
==========================================
Files 20 20
Lines 2220 2228 +8
Branches 470 472 +2
==========================================
+ Hits 2136 2140 +4
- Misses 20 22 +2
- Partials 64 66 +2
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #713 +/- ##
==========================================
- Coverage 96.21% 96.05% -0.17%
==========================================
Files 20 20
Lines 2220 2228 +8
Branches 470 472 +2
==========================================
+ Hits 2136 2140 +4
- Misses 20 22 +2
- Partials 64 66 +2
Continue to review full report at Codecov.
|
From scrubbing through the logs at firebase/firebase-admin-node#585 it seems like we can get into a weird loop when
maybeReopenStream
gets called by both theend
anderror
handler, resulting in exponentially increasing calls tobackoffAndWait()
. This can then cause the backoff handler to error on a single network glitch.