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
agoode opened this issue
Jul 30, 2014
· 3 comments
· Fixed by #331
Assignees
Labels
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
I do pipe the readable stream if there's no multipart required (no resource). If we need to form the multipart body, I use multipart-stream to build the streamable multipart and pipe that to req.
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
I am doing this:
test.mp4
is 3.7GB. top shows that node is using 3.862GB of RAM. I noticed this when I used progress-stream and saw it go immediately to 100%.The text was updated successfully, but these errors were encountered: