Silent fail when fs.inotify.max_user_watches is exceeded
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 111
- Avg merge
- 11h 16m
- Merged PRs (30d)
- 5
Description
Docker container configuration
- Webpack 1.10.3
- Node v0.10.25
- Ubuntu 15.04
Host configuration
- Docker 1.0.1
- Ubuntu 14.04
Issue
Running webpack --watch in docker container successfully performs one build and then exits with exit code 0 (success).
Expectation
Some kind of error code and a return code != 0 if max_user_watches is exceeded.
Workaround
Increasing /proc/sys/fs/inotify/max_user_watches on the host system fixes the problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce webpack --watch in the described Docker and Ubuntu setup with inotify.max_user_watches exceeded, then inspect the watcher entry point that handles the resulting exit. Done means the failure is surfaced as an error with a non-zero exit code instead of a successful exit after the initial build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, nodejs
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100