wasp-bin: script: streamingProcess: exec: invalid argument (Bad file descriptor) on wasp db migrate
Im getting this error after running wasp db migrate-dev on a project. Wasp Version: 0.16.6 node: v20.19.2. I have run wasp clean, deleted and reinstalled both node and wasp. It seems to happen across all wasp projects i create.
5 Replies
Hi @RyanGG. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources do not contain any information about the specific error message:
when running
wasp db migrate-dev.
However, I do see that Wasp currently requires Node.js 18.x, and using Node.js 20.x can cause compatibility issues. Multiple sources indicate that running Wasp with Node.js 20.x is not officially supported in the current version, and users are advised to use Node.js 18.x instead. For example:
In the current version, Wasp requires the use of Node.js 18, but in the coming days we'll update the requirement to be >= 18, so 20 will be supported. In the meantime, consider installingnot working with Node 20.11.0 (Discord)nvmand using Node.js 18 with Wasp 🙂 Quick Start Requirements
Your Node version does not meet Wasp's requirements! You are running Node 20.8.1. Wasp requires Node ^18.12.0 to be installed and in PATH.Error] Node requirement not met (GitHub) Given this, I recommend switching to Node.js 18.x using a tool like
nvm and then trying your command again. If the problem persists after switching to Node.js 18.x, the knowledge sources do not provide further troubleshooting steps for this specific error.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @RyanGG, 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?This happened once before, but we couldn't get to the bottom of it
I think it's Prisma-related
So let's do this, check this thread here: https://discord.com/channels/686873244791210014/1224750529884852396/1224750529884852396
See if the steps tell you anything, if not, report back
and we'll figure it out
I will leave it for @miho though because I'm off next week
I believe it may have something to do with the OS, as the error seems to have started a couple of days ago, around the same time I upgraded from Fedora 41 to 42. I installed Ubuntu 24.04.2 on an old laptop and I am not having this issue on that machine. Similar to that thread, running the template express server does not throw any errors and it seems to run fine.
If you could maybe zip up the problematic project and share it with us? So we can maybe inspect the project and rule out
node_modules.Any updates on this? I got the same error message in HLS (not in Wasp). I doubt the error came from the same place but the problem to uncovering the cause seems to lie in the bad error messaging of the
process library. Anyway this is puzzling because Bad file descriptor is the description of EBADF which the exec family shouldn't be returning.