Error installing cargo-watch on M4 Mac

[thegreathir]

Command:

cargo install cargo-watch

Error:

error[E0283]: type annotations needed
  --> /Users/XXX/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/notify-rust-4.11.5/src/timeout.rs:50:51
   |
50 |         } else if duration.as_millis() > u32::MAX.into() {
   |                                        -          ^^^^
   |                                        |
   |                                        type must be known at this point
   |
   = note: multiple `impl`s satisfying `u128: PartialOrd<_>` found in the following crates: `core`, `deranged`:
           - impl PartialOrd for u128;
           - impl<MIN, MAX> PartialOrd<deranged::RangedU128<MIN, MAX>> for u128
             where the constant `MIN` has type `u128`, the constant `MAX` has type `u128`;
help: try using a fully qualified path to specify the expected types
   |
50 |         } else if duration.as_millis() > <u32 as Into<T>>::into(u32::MAX) {
   |                                          +++++++++++++++++++++++        ~

Compiler version:

➜  ~ rustc --version --verbose
rustc 1.85.1 (4eb161250 2025-03-15)
binary: rustc
commit-hash: 4eb161250e340c8f48f66e2b929ef4a5bed7c181
commit-date: 2025-03-15
host: aarch64-apple-darwin
release: 1.85.1
LLVM version: 19.1.7

[bjorn3]

Does cargo install --locked cargo-watch work?

[thegreathir]

Yes it solved,
It installed Compiling notify-rust v4.11.3

[bjorn3]

In that case it is likely a dependency update that caused this. Given that this is an inference failure, it may not even be a semver breaking change according to the rust semver stability rules. In any case it is not something rustc can do anything about.

[thegreathir]

OK, you can close this,
Should I go ahead and submit an issue on rust-notify repo?

[saethlin]

You should check if cargo-watch already advises you to pass --locked to avoid this situation. Many projects do.

[thegreathir]

Cargo watch seems archived unfortunately,
Probably I should keep in touch with Graphite to migrate to something else.

Thanks

[trinity-1686a]

on a different project, we tracked a similar error to be the consequence of deranged 0.4.1 adding a impl PartialOrd<u64> for RangedU64<_, _> (and similar for other integer types)