-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Error: stream.push() after EOF when making multiple http requests #1822
Comments
yes same here ... developing a downloader application in node-webkit. Works great except for this, PLEASE could you get it fixed. |
+1 |
Thanks for reporting. I'll fix it soon. |
+1 Running into errors with a download manager-like situation. Always comes back to this. |
Would this be fixed with the release of v0.10.0-rc1? |
v0.10.0-rc1 is already published (Jun 22) and thus you may check it. |
Thanks, I haven't run into this error since updating to 10.0-rc1 |
This should be working with latest version now. In 0.13 we changed to an optimized architecture so more features can be supported, see http://nwjs.io/blog/whats-new-in-0.13/ and it's good for keeping up with Chromium upstream -- we released with Node.js v6.0 and new Chromium versions within 1 day after upstream release. The new version would fixed many issues reported here and we're scrubbing them. This issue is closed as we believe it should be fixed. Please leave a message if it isn't and we'll reopen it. |
nodejs/node-v0.x-archive#5439
This is a nodejs bug that's been fixed almost a month ago, but the version that node-webkit is using seems to be outdated. My project is doing a lot of downloading so this bug pretty much renders it useless. Is it possible to update the nodejs version any time soon?
Awesome piece of software you're working on by the way, loving it!
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: