resource exhausted (Too many open files)
This is not the first time that this happens, for some still unknown reason, when doing any file change, instead of recompiling as it should, my
wasp start stops and throw a resource exhausted (Too many open files) error.
I tried wasp clean but didn't work. My project is totally unusable, any change I do breaks wasp start
It's a haskell error, but I'm not sure why it's happening.7 Replies
Hi @abiroot. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
This error is likely due to the number of files being watched by Wasp exceeding the default limit of open files. This issue has been reported in the Wasp community and is currently being investigated (source (https://github.com/wasp-lang/wasp/issues/1844)).
A temporary workaround suggested by a community member is to increase the limit of files that can be open at the same time. You can do this by running the command
ulimit -n 10000 (source (https://discord.com/channels/686873244791210014/1212533517360177253)).
Another potential cause of this issue could be redundant file watches. Wasp watches all files at the top level and then watches the directories src/ and public/ recursively. If node_modules is being watched, this could explain the issue. However, this is still under investigation (source (https://discord.com/channels/686873244791210014/1212533517360177253)).
If you continue to experience this issue, it would be helpful to provide more information on the Wasp GitHub issues page. This could include the version of Wasp you are using, the specific steps you took before encountering the error, and any error messages you received.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @abiroot, 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?I wish I had haskell experience so I could help debug this. From what it seems, haskell is one of the hardest languages right there xD
Wohooo @abiroot, you just became a Waspeteer level 2!
Ok not working at all. Any change I do breaks
wasp startOk if this might help anyone debugging this, when I did
npx tsc --noEmit I got these errors:It worked after doing:
npm install @stitches/react
npm cache clean --force
npm install
npm install --save-dev @types/jest
ulimit -n 10000Thanks for the update here. Seems like a combination of the amount of files watched + a specific stitches error? @martinsos and @sodic would probably be the best people to provide more info here. They will be back on Monday so tagging them until then 🙂