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: Cannot switch to old mode now. #23
Comments
you're probably using the stream somewhere else as well, which you shouldn't be doing (except for maybe pipes) |
@fabdrol can you post what "line 33" refers to? Right is it is |
Sorry, it's line 40/41 in the code in the repo:
|
I think I see the problem. It looks like |
Actually, sorry, re-opening. |
So what we need to do here is determine if the stream is in old mode or not. If it is in old mode, we need to |
@fabdrol I am working on a fix. It doesn't look like |
Nevermind, I was wrong on why the error is cause. It's because |
@dougwilson hmm, okay. Good to know some background. Is the issue specific to the older version, or would a newer version have the same problems? |
All versions have the same problem. It's an issue with now |
Ps, if this is not an issue with this module but with skipper, we can close this right? |
@fabdrol I was going to close it when I made this module provide a better response to the situation, but we can close it regardless, because yes, the issue you reported is cause by what |
@dougwilson okay, thanks for your help anyway! |
No problem. I just posted a possible fix to |
I'm using https://github.com/balderdashy/skipper to upload files in a sails js application, which gave the error
Error: Cannot switch to old mode now
. After some digging, I found out that the error is fixed by commenting out line#33
instream-utils/raw-body/index.js
. It seems to be related to this issue: https://github.com/balderdashy/skipper/issues/10.While I'm convinced this is an issue related to
balderdashy/skipper
specifically, I'm posting this here anyway - maybe you guys can shed some light on this issue.Cheers, Fabian
The text was updated successfully, but these errors were encountered: