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
In short: when a long, chunked GET request sends data, it's possible to get in a state where data is no longer sent, even when additional write events occur. I'm having trouble identifying the root cause, but the above test case makes the situation reproducible & should help anyone with internal knowledge of node-spdy.
Strangely, when adding DEBUG=* or more specifically, DEBUG=spdy:stream:server, the problem disappears.
The text was updated successfully, but these errors were encountered:
I've set up a test case here: https://github.com/canadaduane/spdy-braidify-heisenbug
In short: when a long, chunked GET request sends data, it's possible to get in a state where data is no longer sent, even when additional write events occur. I'm having trouble identifying the root cause, but the above test case makes the situation reproducible & should help anyone with internal knowledge of node-spdy.
Strangely, when adding
DEBUG=*
or more specifically,DEBUG=spdy:stream:server
, the problem disappears.The text was updated successfully, but these errors were encountered: