ci: Compilation failure for v0.18.23 with Rust 1.80.0

[mjsteinbaugh]

If eza fails to compile, or if there is a problem during the build process, then please include the following information in your report:

• The exact eza commit you are building (git rev-parse --short HEAD)
• The version of rustc you are compiling it with (rustc --version)
• Your operating system and hardware platform
• The Rust build target (the exact output of rustc --print cfg)

If you are seeing compilation errors, please include the output of the build process.

---

Hi I'm hitting this compilation error on macOS 14.5 with the latest version of Rust (1.80.0):

     Running `rustc --crate-name num_traits --edition=2015 /private/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/tmp.1b28fHqtXz/cargo/registry/src/index.crates.io-6f17d22bba15001f/num-traits-0.2.14/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C panic=abort -C linker-plugin-lto -C codegen-units=1 --check-cfg 'cfg(docsrs)' --check-cfg 'cfg(feature, values("default", "i128", "libm", "std"))' -C metadata=4a0623b2694d378d -C extra-filename=-4a0623b2694d378d --out-dir /var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps -C strip=symbols -L dependency=/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps --cap-lints allow --cfg has_i128 --cfg has_to_int_unchecked`
error[E0282]: type annotations needed for `Box<_>`
  --> /private/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/tmp.1b28fHqtXz/cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.30/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
help: consider giving `items` an explicit type, where the placeholders `_` are specified
   |
83 |     let items: Box<_> = format_items
   |              ++++++++
[...]
For more information about this error, try `rustc --explain E0282`.
error: could not compile `time` (lib) due to 1 previous error

Caused by:
  process didn't exit successfully: `rustc --crate-name time --edition=2021 /private/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/tmp.1b28fHqtXz/cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.30/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C panic=abort -C linker-plugin-lto -C codegen-units=1 --cfg 'feature="alloc"' --cfg 'feature="default"' --cfg 'feature="formatting"' --cfg 'feature="parsing"' --cfg 'feature="std"' --check-cfg 'cfg(docsrs)' --check-cfg 'cfg(feature, values("alloc", "default", "formatting", "large-dates", "local-offset", "macros", "parsing", "quickcheck", "rand", "serde", "serde-human-readable", "serde-well-known", "std", "wasm-bindgen"))' -C metadata=c469927f7dae0790 -C extra-filename=-c469927f7dae0790 --out-dir /var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps -C strip=symbols -L dependency=/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps --extern deranged=/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps/libderanged-58e50072a55f2922.rmeta --extern itoa=/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps/libitoa-e61905da1c951ec5.rmeta --extern powerfmt=/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps/libpowerfmt-3cd9dfb63c70ec9a.rmeta --extern time_core=/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy/release/deps/libtime_core-a847acc602fd3efe.rmeta --cap-lints allow` (exit status: 1)
warning: build failed, waiting for other jobs to finish...
error: failed to compile `eza v0.18.23`, intermediate artifacts can be found at `/var/folders/9b/4gh0pghx1b71jjd0wjh5mj880000gn/T/cargo-installNWjgVy`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

[mjsteinbaugh]

Can confirm this builds on my machine successfully with Rust 1.79.0. This may be an issue not related to eza but the Rust update instead.

[gierens]

eza is "supposed" to be build with Rust 1.70 ... and usually cargo should pick that up automatically from the rust-toolchain.toml, see

eza/rust-toolchain.toml

Line 2 in 6ca47ee

channel = "1.70"

Are you intentionally trying to compile it with a specific version, or does your cargo just ignore the rust-toolchain.toml?

[mjsteinbaugh]

Thanks @gierens I will look into that and get back to you. As far as I know I'm just trying to install with current cargo but not forcing 1.80 explictly to be used. Is there a better way to handle this with cargo?

[cafkafk]

See: #1070, will be solved on thursday next week when this gets released