Can we add this fix to a trouble shooting tip?
- Dominant language
- JavaScript
- Stars
- 12.2k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
for this error:
```
Fatal error: spawn EMFILE
Running "watch" task
Waiting...OK
>> File "app/templates/views/deals/deals.html" changed.
------------------------------------------------------------------------
error: Looks like a Grunt error occurred--
error: Please fix it, then **restart Sails** to continue running tasks (e.g. watching for changes in assets)
error: Or if you're stuck, check out the troubleshooting tips below.
error: Troubleshooting tips:
error:
error: *-> Are "grunt" and related grunt task modules installed locally? Run `npm install` if you're not sure.
error:
error: *-> You might have a malformed LESS, SASS, CoffeeScript file, etc.
error:
error: *-> Or maybe you don't have permissions to access the `.tmp` directory?
error: e.g., `/Users/jonathanodonnell/Off/.tmp` ?
error:
error: If you think this might be the case, try running:
error: sudo chown -R 501 /Users/jonathanodonnell/Off/.tmp
```
Can we also put the suggestion to run the command:
ulimit -n 1000
Contributor guide
Research direction
Start by locating the troubleshooting tips that report the Grunt error shown in the issue. Add the `ulimit -n 1000` suggestion there, and verify that the troubleshooting output presents the command clearly to users encountering `spawn EMFILE`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100