after update from 4.0.3 to 5.0.4: No space left on device

[chabapok]

OS: ubuntu x64 14.04

Аfter update from 4.0.3 to 5.0.4:

$ cargo watch
thread 'main' panicked at 'unable to create watcher: Io(Error { repr: Os { code: 28, message: "No space left on device" } })', /checkout/src/libcore/result.rs:859
note: Run with RUST_BACKTRACE=1 for a backtrace

And with --poll key: cargo watch --poll run ok and works, but consume 100% of cpu.

4.0.3 works ok.

[hcpl]

cargo-watch switched to wrapping watchexec in 5.0.0. Not an owner, but I doubt the problem lies in cargo-watch itself now.

Does watchexec work for you?

P.S. You can also use cargo watch --debug and see if that can help.

P.P.S. Slightly modifying the line of cargo watch --debug beginning with *** Assembled command and passing that to watchexec will do the same as cargo watch.

[chabapok]

The problem is in watchexec (there is 89G free on device):

$ watchexec -- ls -la
thread 'main' panicked at 'unable to create watcher: Io(Error { repr: Os { code: 28, message: "No space left on device" } })', /checkout/src/libcore/result.rs:859
note: Run with RUST_BACKTRACE=1 for a backtrace.
Aborted (core dumped)

[hcpl]

Try to file this issue to https://github.com/mattgreen/watchexec then.

[chabapok]

Ok

[chabapok]

cargo watch --poll --debug show:

... poll: true, poll_interval: 1

As far as i understand, watcher consume 100% CPU, because default poll intervel ==1, but 500...2000 is better for default.

[passcod]

Hmm, must have misread the docs when I implemented that, I meant 1 second, not millisecond.

[passcod]

Also the "no space left on device" is probably a watcher limit.

[passcod]

(I wrote both cargo watch and notify, the library watchexec uses. This is a fairly frequent error.)

[passcod]

Both fixed/documented in 5.0.5.

Thanks for helping @hcpl!

[hcpl]

@passcod no problem!

And there are two things I'd like to mention:

• It would be useful to have a FAQ for notify too since the root cause is there, move/duplicate questions regarding low-level details from cargo-watch FAQ and add a link to it from cargo-watch. watchexec can also have a FAQ of its own which links to notify; in this case cargo-watch should mention watchexec FAQ too.
• http://blog.sorah.jp is down for now, so http://blog.sorah.jp/2012/01/24/inotify-limitation always returns "502 Bad Gateway". Fortunately it can be replaced by the most recent Web Archive snapshot (http://web.archive.org/web/20161106193425/http://blog.sorah.jp:80/2012/01/24/inotify-limitation).

[passcod]

I'll get onto that, thanks for the feedback :)