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
Expect:
The underlying download stream should also get destroyed.
Actual:
The download stream is still receiving data. This can be verified by running netstat --tcp and see the connection to Azure Blob is still in ESTABLISHED state, and Recv-Q indicates incoming data.
Looking at our core-http code, we pass a abortSignal to node-fetch, however, after we got response back, we removed the listener. It seems an issue to me, as we would want to the ability to cancel the underlying download stream.
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Oct 23, 2020
using code similar to following to download a big file then abort the operation
Expect:
The underlying download stream should also get destroyed.
Actual:
The download stream is still receiving data. This can be verified by running
netstat --tcp
and see the connection to Azure Blob is still inESTABLISHED
state, andRecv-Q
indicates incoming data.Looking at our core-http code, we pass a abortSignal to node-fetch, however, after we got response back, we removed the listener. It seems an issue to me, as we would want to the ability to cancel the underlying download stream.
The text was updated successfully, but these errors were encountered: