[INFO] fetching crate horsetab 0.3.15... [INFO] checking horsetab-0.3.15 against try#ccf408f4326a858c00dd845a64a86b16f360a801 for pr-129466-2 [INFO] extracting crate horsetab 0.3.15 into /workspace/builds/worker-2-tc2/source [INFO] validating manifest of crates.io crate horsetab 0.3.15 on toolchain ccf408f4326a858c00dd845a64a86b16f360a801 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate horsetab 0.3.15 [INFO] finished tweaking crates.io crate horsetab 0.3.15 [INFO] tweaked toml for crates.io crate horsetab 0.3.15 written to /workspace/builds/worker-2-tc2/source/Cargo.toml [INFO] crate crates.io crate horsetab 0.3.15 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] e2041ca3bfa987741a14aeba7f911a2e5951575b90321b8e40bfc88c501024be [INFO] running `Command { std: "docker" "start" "-a" "e2041ca3bfa987741a14aeba7f911a2e5951575b90321b8e40bfc88c501024be", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "e2041ca3bfa987741a14aeba7f911a2e5951575b90321b8e40bfc88c501024be", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e2041ca3bfa987741a14aeba7f911a2e5951575b90321b8e40bfc88c501024be", kill_on_drop: false }` [INFO] [stdout] e2041ca3bfa987741a14aeba7f911a2e5951575b90321b8e40bfc88c501024be [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+ccf408f4326a858c00dd845a64a86b16f360a801" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 831815f4d60244729afa2e342070be275772c98a22536d2b479a26101c39f450 [INFO] running `Command { std: "docker" "start" "-a" "831815f4d60244729afa2e342070be275772c98a22536d2b479a26101c39f450", kill_on_drop: false }` [INFO] [stderr] Copying to /tmp/fixit [INFO] [stderr] Running `cargo fix --edition` [INFO] [stderr] Migrating Cargo.toml from 2021 edition to 2024 [INFO] [stderr] Compiling libc v0.2.149 [INFO] [stderr] Compiling proc-macro2 v1.0.69 [INFO] [stderr] Compiling pkg-config v0.3.27 [INFO] [stderr] Checking bitflags v2.4.1 [INFO] [stderr] Checking memchr v2.6.4 [INFO] [stderr] Checking once_cell v1.18.0 [INFO] [stderr] Checking itoa v1.0.9 [INFO] [stderr] Compiling futures-core v0.3.28 [INFO] [stderr] Compiling rustix v0.38.20 [INFO] [stderr] Checking linux-raw-sys v0.4.10 [INFO] [stderr] Compiling futures-task v0.3.28 [INFO] [stderr] Compiling serde v1.0.190 [INFO] [stderr] Checking log v0.4.20 [INFO] [stderr] Compiling indexmap v1.9.3 [INFO] [stderr] Compiling futures-util v0.3.28 [INFO] [stderr] Compiling openssl v0.10.57 [INFO] [stderr] Checking http v0.2.9 [INFO] [stderr] Checking tracing-core v0.1.32 [INFO] [stderr] Compiling proc-macro-error-attr v1.0.4 [INFO] [stderr] Checking httpdate v1.0.3 [INFO] [stderr] Checking hashbrown v0.12.3 [INFO] [stderr] Checking futures-sink v0.3.28 [INFO] [stderr] Compiling futures-channel v0.3.28 [INFO] [stderr] Checking percent-encoding v2.3.0 [INFO] [stderr] Checking futures-io v0.3.28 [INFO] [stderr] Compiling crc32fast v1.3.2 [INFO] [stderr] Compiling mime_guess v2.0.4 [INFO] [stderr] Checking unicode-normalization v0.1.22 [INFO] [stderr] Compiling proc-macro-error v1.0.4 [INFO] [stderr] Compiling num-traits v0.2.17 [INFO] [stderr] Checking form_urlencoded v1.2.0 [INFO] [stderr] Checking tracing v0.1.40 [INFO] [stderr] Checking unicode-bidi v0.3.13 [INFO] [stderr] Checking ryu v1.0.15 [INFO] [stderr] Checking try-lock v0.2.4 [INFO] [stderr] Checking alloc-no-stdlib v2.0.4 [INFO] [stderr] Checking ppv-lite86 v0.2.17 [INFO] [stderr] Checking fastrand v2.0.1 [INFO] [stderr] Checking want v0.3.1 [INFO] [stderr] Checking alloc-stdlib v0.2.2 [INFO] [stderr] Compiling x11 v2.21.0 [INFO] [stderr] Checking anstyle-parse v0.2.2 [INFO] [stderr] Compiling quote v1.0.33 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling serde_json v1.0.107 [INFO] [stderr] Checking powerfmt v0.2.0 [INFO] [stderr] Checking anstyle v1.0.4 [INFO] [stderr] Compiling syn v2.0.38 [INFO] [stderr] Checking num_cpus v1.16.0 [INFO] [stderr] Checking mio v0.8.9 [INFO] [stderr] Checking socket2 v0.5.5 [INFO] [stderr] Checking getrandom v0.2.10 [INFO] [stderr] Checking idna v0.4.0 [INFO] [stderr] Checking socket2 v0.4.10 [INFO] [stderr] Checking safemem v0.3.3 [INFO] [stderr] Checking anstyle-query v1.0.0 [INFO] [stderr] Checking http-body v0.4.5 [INFO] [stderr] Checking rand_core v0.6.4 [INFO] [stderr] Checking buf_redux v0.8.4 [INFO] [stderr] Compiling cc v1.0.83 [INFO] [stderr] Checking anstream v0.6.4 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Checking deranged v0.3.9 [INFO] [stderr] Checking gzip-header v1.0.0 [INFO] [stderr] Checking brotli-decompressor v2.5.0 [INFO] [stderr] Checking twoway v0.1.8 [INFO] [stderr] Checking tokio v1.33.0 [INFO] [stderr] Checking aho-corasick v1.1.2 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Checking iana-time-zone v0.1.58 [INFO] [stderr] Checking home v0.5.5 [INFO] [stderr] Compiling anyhow v1.0.75 [INFO] [stderr] Checking quick-error v1.2.3 [INFO] [stderr] Checking url v2.4.1 [INFO] [stderr] Checking clap_lex v0.5.1 [INFO] [stderr] Checking adler32 v1.2.0 [INFO] [stderr] Checking ascii v1.1.0 [INFO] [stderr] Checking time-core v0.1.2 [INFO] [stderr] Checking strsim v0.10.0 [INFO] [stderr] Checking chunked_transfer v1.4.1 [INFO] [stderr] Checking either v1.9.0 [INFO] [stderr] Checking num_threads v0.1.6 [INFO] [stderr] Checking clap_builder v4.4.6 [INFO] [stderr] Checking deflate v1.0.0 [INFO] [stderr] Checking tiny_http v0.12.0 [INFO] [stderr] Checking threadpool v1.8.1 [INFO] [stderr] Checking filetime v0.2.22 [INFO] [stderr] Checking chrono v0.4.31 [INFO] [stderr] Checking base64 v0.13.1 [INFO] [stderr] Checking sha1_smol v1.0.0 [INFO] [stderr] Checking tempfile v3.8.0 [INFO] [stderr] Checking time v0.3.30 [INFO] [stderr] Checking which v4.4.2 [INFO] [stderr] Checking is-terminal v0.4.9 [INFO] [stderr] Checking base64 v0.21.5 [INFO] [stderr] Checking colored v2.0.4 [INFO] [stderr] Checking multipart v0.18.0 [INFO] [stderr] Checking edit v0.1.4 [INFO] [stderr] Checking brotli v3.4.0 [INFO] [stderr] Compiling openssl-sys v0.9.93 [INFO] [stderr] Checking regex-automata v0.4.3 [INFO] [stderr] Compiling native-tls v0.2.11 [INFO] [stderr] Checking rdev v0.5.3 [INFO] [stderr] Compiling test-case-core v3.2.1 [INFO] [stderr] Checking regex v1.10.2 [INFO] [stderr] Compiling serde_derive v1.0.190 [INFO] [stderr] Compiling openssl-macros v0.1.1 [INFO] [stderr] Compiling clap_derive v4.4.2 [INFO] [stderr] Compiling test-case-macros v3.2.1 [INFO] [stderr] Checking tokio-util v0.7.9 [INFO] [stderr] Checking test-case v3.2.1 [INFO] [stderr] Checking h2 v0.3.21 [INFO] [stderr] Checking clap v4.4.6 [INFO] [stderr] Checking tokio-native-tls v0.3.1 [INFO] [stderr] Checking hyper v0.14.27 [INFO] [stderr] Checking serde_urlencoded v0.7.1 [INFO] [stderr] Checking bincode v1.3.3 [INFO] [stderr] Checking hyper-tls v0.5.0 [INFO] [stderr] Checking reqwest v0.11.22 [INFO] [stderr] Checking rouille v3.6.2 [INFO] [stderr] Checking horsetab v0.3.15 (/tmp/fixit) [INFO] [stderr] Migrating src/main.rs from 2021 edition to 2024 [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `horsetab` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/server/process_manager.rs [INFO] [stderr] [INFO] [stderr] This likely indicates a bug in either rustc or cargo itself, [INFO] [stderr] and we would appreciate a bug report! You're likely to see [INFO] [stderr] a number of compiler warnings after this message which cargo [INFO] [stderr] attempted to fix but failed. If you could open an issue at [INFO] [stderr] https://github.com/rust-lang/rust/issues [INFO] [stderr] quoting the full output of this command we'd be very appreciative! [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:4 [INFO] [stderr] | [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:20 [INFO] [stderr] | [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:37 [INFO] [stderr] | [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:56 [INFO] [stderr] | [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:9 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr_2021, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: aborting due to 4 previous errors [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr_2021, $status:expr, $cmd:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:35 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr_2021, $cmd:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] For more information about this error, try `rustc --explain E0658`. [INFO] [stderr] Original diagnostics will follow. [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:46 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr_2021) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to deprecated safe function `std::env::set_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/logger.rs:67:5 [INFO] [stdout] | [INFO] [stdout] 67 | std::env::set_var("TZ", "Asia/Tokyo"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = warning: this is accepted in the current edition (Rust 2021) but is a hard error in Rust 2024! [INFO] [stdout] = note: for more information, see issue #27970 [INFO] [stdout] = note: `--force-warn deprecated-safe-2024` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: you can wrap the call in an `unsafe` block if you can guarantee that the environment access only happens in single-threaded code [INFO] [stdout] | [INFO] [stdout] 67 + // TODO: Audit that the environment access only happens in single-threaded code. [INFO] [stdout] 68 ~ unsafe { std::env::set_var("TZ", "Asia/Tokyo") }; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `if let` assigns a shorter lifetime since Edition 2024 [INFO] [stdout] --> src/cli/subcommands.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | while let Ok(event_type) = bincode::deserialize_from(&mut buf) { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^----------------------------------- [INFO] [stdout] | | [INFO] [stdout] | this value has a significant drop implementation which may observe a major change in drop order and requires your discretion [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #124085 [INFO] [stdout] help: the value is now dropped here in Edition 2024 [INFO] [stdout] --> src/cli/subcommands.rs:91:3 [INFO] [stdout] | [INFO] [stdout] 91 | } [INFO] [stdout] | ^ [INFO] [stdout] = note: `--force-warn if-let-rescope` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl for<'a> Fn(&'a rouille::Request) -> rouille::Response` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/server/http.rs:108:20 [INFO] [stdout] | [INFO] [stdout] 108 | ) -> Result Response>, Box> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/server/http.rs:105:16 [INFO] [stdout] | [INFO] [stdout] 105 | config_path: &str, [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit [INFO] [stdout] | [INFO] [stdout] 108 | ) -> Result Response + use<>>, Box> { [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `if let` assigns a shorter lifetime since Edition 2024 [INFO] [stdout] --> src/server/main.rs:31:6 [INFO] [stdout] | [INFO] [stdout] 31 | if let InstallResult::FileError(_) = install_result { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^-------------- [INFO] [stdout] | | [INFO] [stdout] | this value has a significant drop implementation which may observe a major change in drop order and requires your discretion [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #124085 [INFO] [stdout] help: the value is now dropped here in Edition 2024 [INFO] [stdout] --> src/server/main.rs:33:3 [INFO] [stdout] | [INFO] [stdout] 33 | } [INFO] [stdout] | ^ [INFO] [stdout] help: a `match` with a single arm can preserve the drop order up to Edition 2021 [INFO] [stdout] | [INFO] [stdout] 31 ~ match install_result { InstallResult::FileError(_) => { [INFO] [stdout] 32 | std::process::exit(1); [INFO] [stdout] 33 ~ } _ => {}} [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `if let` assigns a shorter lifetime since Edition 2024 [INFO] [stdout] --> src/server/results_command_exec.rs:19:8 [INFO] [stdout] | [INFO] [stdout] 19 | if let Err(e) = start_result { [INFO] [stdout] | ^^^^^^^^^^^^^------------ [INFO] [stdout] | | [INFO] [stdout] | this value has a significant drop implementation which may observe a major change in drop order and requires your discretion [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #124085 [INFO] [stdout] help: the value is now dropped here in Edition 2024 [INFO] [stdout] --> src/server/results_command_exec.rs:21:5 [INFO] [stdout] | [INFO] [stdout] 21 | } [INFO] [stdout] | ^ [INFO] [stdout] help: a `match` with a single arm can preserve the drop order up to Edition 2021 [INFO] [stdout] | [INFO] [stdout] 19 ~ match start_result { Err(e) => { [INFO] [stdout] 20 | eprintln!("{e}"); [INFO] [stdout] 21 ~ } _ => {}} [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 9 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] warning: failed to automatically apply fixes suggested by rustc to crate `horsetab` [INFO] [stderr] [INFO] [stderr] after fixes were automatically applied the compiler reported errors within these files: [INFO] [stderr] [INFO] [stderr] * src/server/process_manager.rs [INFO] [stderr] [INFO] [stderr] This likely indicates a bug in either rustc or cargo itself, [INFO] [stderr] and we would appreciate a bug report! You're likely to see [INFO] [stderr] a number of compiler warnings after this message which cargo [INFO] [stderr] attempted to fix but failed. If you could open an issue at [INFO] [stderr] https://github.com/rust-lang/rust/issues [INFO] [stderr] quoting the full output of this command we'd be very appreciative! [INFO] [stderr] Note that you may be able to make some more progress in the near-term [INFO] [stderr] fixing code with the `--broken-code` flag [INFO] [stderr] [INFO] [stderr] The following errors were reported: [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:4 [INFO] [stderr] | [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:20 [INFO] [stderr] | [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:9 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr_2021, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:37 [INFO] [stderr] | [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:21 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr_2021, $status:expr, $cmd:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error[E0658]: fragment specifier `expr_2021` is unstable [INFO] [stderr] --> src/server/process_manager.rs:38:56 [INFO] [stderr] | [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:35 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr_2021, $cmd:expr) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] 38 | ($pid:expr_2021, $time:expr_2021, $status:expr_2021, $cmd:expr_2021) => { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: see issue #123742 for more information [INFO] [stderr] = help: add `#![feature(expr_fragment_specifier_2024)]` to the crate attributes to enable [INFO] [stderr] = note: this compiler was built on 2024-09-17; consider upgrading it if it is out of date [INFO] [stderr] [INFO] [stderr] error: aborting due to 4 previous errors [INFO] [stderr] [INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition [INFO] [stdout] --> src/server/process_manager.rs:38:46 [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr) => { [INFO] [stdout] | ^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see Migration Guide [INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier [INFO] [stdout] | [INFO] [stdout] 38 | ($pid:expr, $time:expr, $status:expr, $cmd:expr_2021) => { [INFO] [stdout] | ~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] For more information about this error, try `rustc --explain E0658`. [INFO] [stderr] Original diagnostics will follow. [INFO] [stderr] [INFO] [stdout] warning: `if let` assigns a shorter lifetime since Edition 2024 [INFO] [stdout] --> src/cli/subcommands.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | while let Ok(event_type) = bincode::deserialize_from(&mut buf) { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^----------------------------------- [INFO] [stdout] | | [INFO] [stdout] | this value has a significant drop implementation which may observe a major change in drop order and requires your discretion [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #124085 [INFO] [stdout] help: the value is now dropped here in Edition 2024 [INFO] [stdout] --> src/cli/subcommands.rs:91:3 [INFO] [stdout] | [INFO] [stdout] 91 | } [INFO] [stdout] | ^ [INFO] [stdout] = note: `--force-warn if-let-rescope` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `impl for<'a> Fn(&'a rouille::Request) -> rouille::Response` will capture more lifetimes than possibly intended in edition 2024 [INFO] [stdout] --> src/server/http.rs:108:20 [INFO] [stdout] | [INFO] [stdout] 108 | ) -> Result Response>, Box> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see [INFO] [stdout] note: specifically, this lifetime is in scope but not mentioned in the type's bounds [INFO] [stdout] --> src/server/http.rs:105:16 [INFO] [stdout] | [INFO] [stdout] 105 | config_path: &str, [INFO] [stdout] | ^ [INFO] [stdout] = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024 [INFO] [stdout] = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility` [INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit [INFO] [stdout] | [INFO] [stdout] 108 | ) -> Result Response + use<>>, Box> { [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `if let` assigns a shorter lifetime since Edition 2024 [INFO] [stdout] --> src/server/main.rs:31:6 [INFO] [stdout] | [INFO] [stdout] 31 | if let InstallResult::FileError(_) = install_result { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^-------------- [INFO] [stdout] | | [INFO] [stdout] | this value has a significant drop implementation which may observe a major change in drop order and requires your discretion [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #124085 [INFO] [stdout] help: the value is now dropped here in Edition 2024 [INFO] [stdout] --> src/server/main.rs:33:3 [INFO] [stdout] | [INFO] [stdout] 33 | } [INFO] [stdout] | ^ [INFO] [stdout] help: a `match` with a single arm can preserve the drop order up to Edition 2021 [INFO] [stdout] | [INFO] [stdout] 31 ~ match install_result { InstallResult::FileError(_) => { [INFO] [stdout] 32 | std::process::exit(1); [INFO] [stdout] 33 ~ } _ => {}} [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `if let` assigns a shorter lifetime since Edition 2024 [INFO] [stdout] --> src/server/results_command_exec.rs:19:8 [INFO] [stdout] | [INFO] [stdout] 19 | if let Err(e) = start_result { [INFO] [stdout] | ^^^^^^^^^^^^^------------ [INFO] [stdout] | | [INFO] [stdout] | this value has a significant drop implementation which may observe a major change in drop order and requires your discretion [INFO] [stdout] | [INFO] [stdout] = warning: this changes meaning in Rust 2024 [INFO] [stdout] = note: for more information, see issue #124085 [INFO] [stdout] help: the value is now dropped here in Edition 2024 [INFO] [stdout] --> src/server/results_command_exec.rs:21:5 [INFO] [stdout] | [INFO] [stdout] 21 | } [INFO] [stdout] | ^ [INFO] [stdout] help: a `match` with a single arm can preserve the drop order up to Edition 2021 [INFO] [stdout] | [INFO] [stdout] 19 ~ match start_result { Err(e) => { [INFO] [stdout] 20 | eprintln!("{e}"); [INFO] [stdout] 21 ~ } _ => {}} [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: 8 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 17.65s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: buf_redux v0.8.4, multipart v0.18.0 [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1` [INFO] [stderr] Running `cargo check` to verify 2024 [INFO] [stderr] Checking horsetab v0.3.15 (/tmp/fixit) [INFO] [stdout] error[E0521]: borrowed data escapes outside of function [INFO] [stdout] --> src/server/http.rs:131:9 [INFO] [stdout] | [INFO] [stdout] 127 | config_path: &str, [INFO] [stdout] | ----------- - let's call the lifetime of this reference `'1` [INFO] [stdout] | | [INFO] [stdout] | `config_path` is a reference that is only valid in the function body [INFO] [stdout] ... [INFO] [stdout] 131 | match build_http_server(port, tcp_port, config_path, sequence_sender, state) { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | `config_path` escapes the function body here [INFO] [stdout] | argument requires that `'1` must outlive `'static` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 1 previous error [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0521`. [INFO] [stdout] [INFO] [stderr] error: could not compile `horsetab` (bin "horsetab") due to 2 previous errors [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error[E0133]: call to unsafe function `set_var` is unsafe and requires unsafe block [INFO] [stdout] --> src/logger.rs:67:5 [INFO] [stdout] | [INFO] [stdout] 67 | std::env::set_var("TZ", "Asia/Tokyo"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ call to unsafe function [INFO] [stdout] | [INFO] [stdout] = note: consult the function's documentation for information on how to avoid undefined behavior [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0521]: borrowed data escapes outside of function [INFO] [stdout] --> src/server/http.rs:131:9 [INFO] [stdout] | [INFO] [stdout] 127 | config_path: &str, [INFO] [stdout] | ----------- - let's call the lifetime of this reference `'1` [INFO] [stdout] | | [INFO] [stdout] | `config_path` is a reference that is only valid in the function body [INFO] [stdout] ... [INFO] [stdout] 131 | match build_http_server(port, tcp_port, config_path, sequence_sender, state) { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | `config_path` escapes the function body here [INFO] [stdout] | argument requires that `'1` must outlive `'static` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 2 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0133, E0521. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0133`. [INFO] [stdout] [INFO] [stderr] error: could not compile `horsetab` (bin "horsetab" test) due to 3 previous errors [INFO] [stderr] error: failed to check after updating to 2024 [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `cargo check --frozen --all --all-targets --message-format=json` (exit status: 101) [INFO] running `Command { std: "docker" "inspect" "831815f4d60244729afa2e342070be275772c98a22536d2b479a26101c39f450", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "831815f4d60244729afa2e342070be275772c98a22536d2b479a26101c39f450", kill_on_drop: false }` [INFO] [stdout] 831815f4d60244729afa2e342070be275772c98a22536d2b479a26101c39f450