Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Watcher is failing, by default, on Linux

See original GitHub issue

When @Elchi3 tested yarn start it crashes the watcher (with an unhandled error too!) because his system couldn’t cope with that many open files. By default.

He fixed his system by (blindly) following the tips here: https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Somehow we need to cope with this better for our Linux users.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:11 (10 by maintainers)

Top GitHub Comments

2reactions

fiji-flocommented, Nov 6, 2020

I suggest we support running the server without the watcher. Modifying system settings should be a last resort.

It would also be okay to just document this for now as it’s a common issue. But I would prefer making it optional.

0reactions

peterbecommented, Nov 11, 2020

It’s been a while since I looked at that, but what’s wrong with adding a watcher.on("error" …)? As long as we can “inject” a console.log() before it re-throws, I think we can make life easier for people.