streamingProcess: exec: invalid argument (Bad file descriptor) error
I am getting a wasp-bin: /home/~path/app/node_modules/.bin/prisma: streamingProcess: exec: invalid argument (Bad file descriptor) error when I run
wasp db migrate-dev before starting the app even first time.
node version - v22.5.0
npm version - 10.8.2
wasp version - 0.14.0
Have tried wasp clean and retried it didn't work.
I am running wasp on Windows using wsl and using saas template11 Replies
Hi @Swapnil. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. However, based on the knowledge sources, it seems like you've already tried some common troubleshooting steps like
wasp clean and wasp db migrate-dev.
One thing you could try is to manually run npm install in the .wasp/out/web-app and .wasp/out/server folders after running wasp compile for a few minutes and then killing it. This is a way to get more detailed logs and might help identify the issue (source (https://discord.com/channels/686873244791210014/1213593156646604820)).
If you're still having trouble, I would recommend creating an issue on the Wasp Github (https://github.com/wasp-lang/wasp/issues) with the details of your problem. The Wasp community is very active and might be able to help you solve this issue.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Swapnil, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Hey @Swapnil! I'm trying to reproduce it now, I'll let you know how it goes
I'm getting a different error:
Did you get this one?
Also, can you maybe try running the project with node 20 (if you have it handy)?
Did some testing, seems no version of Wasp works for Node 22. It looks like it's thanks to an internal NPM bug
@Swapnil Any chance you can use node 20?
@sodic I checked the logs it mentioned that it is npm internal error, let me try with node 20
I didn't get this error
Yeah, I'm getting that too. Probably the same NPM internal error manifesting in different ways for you and me
Let me know if everything's ok with Node 20
@sodic It is working with Node 20, Node 22 is the issue it seems
Ok yup I can also replicate it
Ok, it is actually bug with newest npm 22.5.0, not realted to Wasp: https://github.com/npm/cli/issues/7657 .
Even just using npm 22.4.0 fixes it. I assume they will soon release a fix.
GitHub
[BUG] Exit handler never called during clean-install, with Node.js ...
Is there an existing issue for this? I have searched the existing issues This issue exists in the latest npm version I am using the latest npm Current Behavior (While there are similar issues alrea...
Documented it here just for people that might be looking: https://github.com/wasp-lang/wasp/issues/2195
GitHub
Wasp not working with node 22.5.0 (this is npm bug, not Wasp!) · Is...
This is npm bug that happens only with node 22.5 which was just released: npm/cli#7657 . I assume it will be resolved soon but I am still documenting this in case Wasp users start looking at the Wa...
alright, thanks for the update