You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 16, 2023. It is now read-only.
When using request the end events are sometimes fired multiple times. This is because request includes a fix for a bug in node core. request will fire an end when it see a close event if it hasn't yet seen an end event. Sometimes request is receiving the close event from node-replay first which causes it to fire an end event and then request receives the end event from node-replay and fires anotherend event.
When using request the
end
events are sometimes fired multiple times. This is because request includes a fix for a bug in node core. request will fire anend
when it see aclose
event if it hasn't yet seen anend
event. Sometimes request is receiving theclose
event from node-replay first which causes it to fire anend
event and then request receives theend
event from node-replay and fires anotherend
event.A quick fix is disabling these lines of code but I don't know if that would have any unintended consequences.
I believe it only occurs on some requests because it's a race condition.
The text was updated successfully, but these errors were encountered: