wasp: Fix error during `wasp start` after `wasp start` and failing `wasp build`
Version: 0.13.2. (probably post-0.12.0 and caused by https://github.com/wasp-lang/wasp/issues/1769#issuecomment-1952938100, doesn’t happen with 0.11.8).
OS: Linux
How to reproduce:
- Run
wasp new something && cd something. - Run
wasp startand wait for it to finish. - Run
wasp buildand see it fail because of an inappropriate database (SQLLite). - Run
wasp startagain and see the error.
Here’s how it looks in action:
$ wasp start
🐝 --- Starting compilation and setup phase. Hold tight... ------------------------
🐝 --- Compiling wasp project... --------------------------------------------------
✅ --- Successfully completed npm install. ----------------------------------------
🐝 --- Setting up database... -----------------------------------------------------
✅ --- Database successfully set up. ----------------------------------------------
🐝 --- Building SDK... ------------------------------------------------------------
wasp-bin: npx: streamingProcess: chdir: invalid argument (Bad file descriptor)
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 19 (9 by maintainers)
Hey @Rotemoyal, thanks for letting us know!
It’s not ideal, but you should be able to fix it by running
wasp cleanafter any command throws this error, and then rerunning the command.wasp cleanwon’t delete anything important, it only cleans up the build artifacts, so no worries.This solved my issue, thanks. I ran this command first
wasp clean. Then I ranwasp startHad the same issue with Ubuntu 24.04 and node 18. For me it helped to upgrade node to 20 and doing a fresh wasp new.
Definitely! I just made a new issue to track it: https://github.com/wasp-lang/wasp/issues/2113
Thanks for letting us know 😃