[INFO] cloning repository https://github.com/abuaasifaahil/uv [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/abuaasifaahil/uv" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fabuaasifaahil%2Fuv", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fabuaasifaahil%2Fuv'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] e09fe28e596938a17a987e46280749c4b6866793 [INFO] checking abuaasifaahil/uv against master#23718020b12d7e5a54f82a19910e8356ee719667 for pr-146013-1 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fabuaasifaahil%2Fuv" "/workspace/builds/worker-2-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-2-tc1/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-2-tc1/source/.cargo/config.toml [INFO] removed /workspace/builds/worker-2-tc1/source/rust-toolchain.toml [INFO] started tweaking git repo https://github.com/abuaasifaahil/uv [INFO] finished tweaking git repo https://github.com/abuaasifaahil/uv [INFO] tweaked toml for git repo https://github.com/abuaasifaahil/uv written to /workspace/builds/worker-2-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/abuaasifaahil/uv on toolchain 23718020b12d7e5a54f82a19910e8356ee719667 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+23718020b12d7e5a54f82a19910e8356ee719667" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/abuaasifaahil/uv 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" "+23718020b12d7e5a54f82a19910e8356ee719667" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Updating git repository `https://github.com/charliermarsh/rs-async-zip` [INFO] [stderr] Updating git repository `https://github.com/astral-sh/pubgrub` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded which v6.0.1 [INFO] [stderr] Downloaded pathdiff v0.2.1 [INFO] [stderr] Downloaded serde_derive_internals v0.29.0 [INFO] [stderr] Downloaded owo-colors v4.0.0 [INFO] [stderr] Downloaded http-content-range v0.1.2 [INFO] [stderr] Downloaded schemars v0.8.17 [INFO] [stderr] Downloaded predicates-core v1.0.6 [INFO] [stderr] Downloaded configparser v3.0.4 [INFO] [stderr] Downloaded serde_json v1.0.116 [INFO] [stderr] Downloaded bstr v1.9.1 [INFO] [stderr] Downloaded miette-derive v7.2.0 [INFO] [stderr] Downloaded async_http_range_reader v0.8.0 [INFO] [stderr] Downloaded pretty_assertions v1.4.0 [INFO] [stderr] Downloaded axoprocess v0.2.0 [INFO] [stderr] Downloaded rustls-pemfile v2.1.2 [INFO] [stderr] Downloaded nu-ansi-term v0.49.0 [INFO] [stderr] Downloaded svgfilters v0.4.0 [INFO] [stderr] Downloaded codspeed-criterion-compat v2.6.0 [INFO] [stderr] Downloaded codspeed v2.6.0 [INFO] [stderr] Downloaded axotag v0.2.0 [INFO] [stderr] Downloaded oorandom v11.1.3 [INFO] [stderr] Downloaded assert_cmd v2.0.14 [INFO] [stderr] Downloaded float-cmp v0.9.0 [INFO] [stderr] Downloaded priority-queue v2.0.2 [INFO] [stderr] Downloaded gif v0.12.0 [INFO] [stderr] Downloaded rosvgtree v0.1.0 [INFO] [stderr] Downloaded libmimalloc-sys v0.1.37 [INFO] [stderr] Downloaded miette v7.2.0 [INFO] [stderr] Downloaded resvg v0.29.0 [INFO] [stderr] Downloaded kurbo v0.8.3 [INFO] [stderr] Downloaded usvg v0.29.0 [INFO] [stderr] Downloaded pyo3-ffi v0.21.2 [INFO] [stderr] Downloaded pyo3 v0.21.2 [INFO] [stderr] Downloaded brotli v5.0.0 [INFO] [stderr] Downloaded pest v2.7.8 [INFO] [stderr] Downloaded zstd-sys v2.0.10+zstd.1.5.6 [INFO] [stderr] Downloaded webpki-roots v0.26.1 [INFO] [stderr] Downloaded libz-sys v1.1.16 [INFO] [stderr] Downloaded axoupdater v0.6.1 [INFO] [stderr] Downloaded tracing-durations-export v0.2.0 [INFO] [stderr] Downloaded kurbo v0.9.5 [INFO] [stderr] Downloaded vte v0.11.1 [INFO] [stderr] Downloaded event-listener-strategy v0.5.1 [INFO] [stderr] Downloaded wiremock v0.6.0 [INFO] [stderr] Downloaded pest_meta v2.7.8 [INFO] [stderr] Downloaded similar v2.5.0 [INFO] [stderr] Downloaded insta v1.38.0 [INFO] [stderr] Downloaded toml v0.8.12 [INFO] [stderr] Downloaded zstd-safe v7.1.0 [INFO] [stderr] Downloaded thiserror-impl v1.0.59 [INFO] [stderr] Downloaded socket2 v0.5.6 [INFO] [stderr] Downloaded windows v0.56.0 [INFO] [stderr] Downloaded windows-core v0.56.0 [INFO] [stderr] Downloaded tl v0.7.8 [INFO] [stderr] Downloaded windows-interface v0.56.0 [INFO] [stderr] Downloaded pest_generator v2.7.8 [INFO] [stderr] Downloaded clap_builder v4.5.2 [INFO] [stderr] Downloaded assert-json-diff v2.0.2 [INFO] [stderr] Downloaded pyo3-log v0.10.0 [INFO] [stderr] Downloaded rustls-native-certs v0.7.0 [INFO] [stderr] Downloaded fs-err v2.11.0 [INFO] [stderr] Downloaded rustls v0.22.3 [INFO] [stderr] Downloaded retry-policies v0.3.0 [INFO] [stderr] Downloaded clap v4.5.4 [INFO] [stderr] Downloaded quoted_printable v0.5.0 [INFO] [stderr] Downloaded pest_derive v2.7.8 [INFO] [stderr] Downloaded unscanny v0.1.0 [INFO] [stderr] Downloaded pyo3-macros v0.21.2 [INFO] [stderr] Downloaded globset v0.4.14 [INFO] [stderr] Downloaded http-body-util v0.1.1 [INFO] [stderr] Downloaded displaydoc v0.2.4 [INFO] [stderr] Downloaded target-lexicon v0.12.14 [INFO] [stderr] Downloaded hyper-util v0.1.3 [INFO] [stderr] Downloaded thiserror v1.0.59 [INFO] [stderr] Downloaded zip v1.1.4 [INFO] [stderr] Downloaded cachedir v0.3.1 [INFO] [stderr] Downloaded wait-timeout v0.2.0 [INFO] [stderr] Downloaded wmi v0.13.3 [INFO] [stderr] Downloaded clap_complete_nushell v0.1.11 [INFO] [stderr] Downloaded is_ci v1.2.0 [INFO] [stderr] Downloaded poloto v19.1.2 [INFO] [stderr] Downloaded libz-ng-sys v1.1.15 [INFO] [stderr] Downloaded rustls-webpki v0.102.2 [INFO] [stderr] Downloaded yansi v0.5.1 [INFO] [stderr] Downloaded winnow v0.6.5 [INFO] [stderr] Downloaded cc v1.0.92 [INFO] [stderr] Downloaded fontdb v0.12.0 [INFO] [stderr] Downloaded simplecss v0.2.1 [INFO] [stderr] Downloaded svgtypes v0.9.0 [INFO] [stderr] Downloaded usvg-text-layout v0.29.0 [INFO] [stderr] Downloaded vte_generate_state_changes v0.1.1 [INFO] [stderr] Downloaded vt100 v0.15.2 [INFO] [stderr] Downloaded tracing-indicatif v0.3.6 [INFO] [stderr] Downloaded async-channel v2.2.1 [INFO] [stderr] Downloaded predicates v3.1.0 [INFO] [stderr] Downloaded platform-info v2.0.3 [INFO] [stderr] Downloaded reflink-copy v0.1.17 [INFO] [stderr] Downloaded reqwest-retry v0.5.0 [INFO] [stderr] Downloaded sys-info v0.9.1 [INFO] [stderr] Downloaded reqwest-middleware v0.3.0 [INFO] [stderr] Downloaded rust-netrc v0.1.1 [INFO] [stderr] Downloaded test-log-macros v0.2.15 [INFO] [stderr] Downloaded test-log v0.2.16 [INFO] [stderr] Downloaded deadpool-runtime v0.1.3 [INFO] [stderr] Downloaded clap_derive v4.5.4 [INFO] [stderr] Downloaded charset v0.1.3 [INFO] [stderr] Downloaded mailparse v0.15.0 [INFO] [stderr] Downloaded indoc v2.0.5 [INFO] [stderr] Downloaded pyo3-macros-backend v0.21.2 [INFO] [stderr] Downloaded async-compression v0.4.9 [INFO] [stderr] Downloaded h2 v0.4.4 [INFO] [stderr] Downloaded camino v1.1.6 [INFO] [stderr] Downloaded windows-implement v0.52.0 [INFO] [stderr] Downloaded homedir v0.2.1 [INFO] [stderr] Downloaded temp-dir v0.1.13 [INFO] [stderr] Downloaded clap_complete_fig v4.5.0 [INFO] [stderr] Downloaded clap_complete_command v0.5.1 [INFO] [stderr] Downloaded backtrace-ext v0.2.1 [INFO] [stderr] Downloaded tracing-tree v0.3.0 [INFO] [stderr] Downloaded doc-comment v0.3.3 [INFO] [stderr] Downloaded normalize-line-endings v0.3.0 [INFO] [stderr] Downloaded windows-implement v0.56.0 [INFO] [stderr] Downloaded pyo3-build-config v0.21.2 [INFO] [stderr] Downloaded testing_logger v0.1.1 [INFO] [stderr] Downloaded ignore v0.4.22 [INFO] [stderr] Downloaded cargo-util v0.2.11 [INFO] [stderr] Downloaded openssl-sys v0.9.102 [INFO] [stderr] Downloaded toml_edit v0.22.9 [INFO] [stderr] Downloaded fs2 v0.4.3 [INFO] [stderr] Downloaded pico-args v0.5.0 [INFO] [stderr] Downloaded tiny-skia-path v0.8.4 [INFO] [stderr] Downloaded roxmltree v0.19.0 [INFO] [stderr] Downloaded unicode-general-category v0.6.0 [INFO] [stderr] Downloaded imagesize v0.11.0 [INFO] [stderr] Downloaded tagu v0.1.6 [INFO] [stderr] Downloaded svg v0.15.1 [INFO] [stderr] Downloaded directories v5.0.1 [INFO] [stderr] Downloaded anyhow v1.0.82 [INFO] [stderr] Downloaded brotli-decompressor v4.0.0 [INFO] [stderr] Downloaded security-framework v2.10.0 [INFO] [stderr] Downloaded tokio-tar v0.3.1 [INFO] [stderr] Downloaded encoding_rs_io v0.1.7 [INFO] [stderr] Downloaded axoasset v0.9.1 [INFO] [stderr] Downloaded windows-interface v0.52.0 [INFO] [stderr] Downloaded clap_complete v4.5.2 [INFO] [stderr] Downloaded supports-color v3.0.0 [INFO] [stderr] Downloaded tiny-skia v0.8.4 [INFO] [stderr] Downloaded ttf-parser v0.18.1 [INFO] [stderr] Downloaded rustybuzz v0.7.0 [INFO] [stderr] Downloaded unindent v0.2.3 [INFO] [stderr] Downloaded zstd v0.13.1 [INFO] [stderr] Downloaded security-framework-sys v2.10.0 [INFO] [stderr] Downloaded path-dedot v3.1.1 [INFO] [stderr] Downloaded rctree v0.5.0 [INFO] [stderr] Downloaded csv v1.3.0 [INFO] [stderr] Downloaded hyper-rustls v0.26.0 [INFO] [stderr] Downloaded hyper v1.3.1 [INFO] [stderr] Downloaded fastrand v2.0.2 [INFO] [stderr] Downloaded mimalloc v0.1.41 [INFO] [stderr] Downloaded svgtypes v0.10.0 [INFO] [stderr] Downloaded fontconfig-parser v0.5.6 [INFO] [stderr] Downloaded unicode-script v0.5.6 [INFO] [stderr] Downloaded unicode-vo v0.1.0 [INFO] [stderr] Downloaded data-url v0.2.0 [INFO] [stderr] Downloaded junction v1.1.0 [INFO] [stderr] Downloaded xattr v1.3.1 [INFO] [stderr] Downloaded cmake v0.1.50 [INFO] [stderr] Downloaded dunce v1.0.4 [INFO] [stderr] Downloaded rustls-pki-types v1.4.1 [INFO] [stderr] Downloaded path-absolutize v3.1.1 [INFO] [stderr] Downloaded rgb v0.8.37 [INFO] [stderr] Downloaded roxmltree v0.18.1 [INFO] [stderr] Downloaded ctrlc v3.4.4 [INFO] [stderr] Downloaded difflib v0.4.0 [INFO] [stderr] Downloaded serde_spanned v0.6.5 [INFO] [stderr] Downloaded serde_derive v1.0.200 [INFO] [stderr] Downloaded syn v2.0.58 [INFO] [stderr] Downloaded serde v1.0.200 [INFO] [stderr] Downloaded predicates-tree v1.0.9 [INFO] [stderr] Downloaded assert_fs v1.1.1 [INFO] [stderr] Downloaded bisection v0.1.0 [INFO] [stderr] Downloaded schemars_derive v0.8.17 [INFO] [stderr] Downloaded openssl-src v300.2.3+3.2.1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+23718020b12d7e5a54f82a19910e8356ee719667" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 7eb0e93be69ca8d6138fcb4af7a77da21fa40afa2c0686f2a5b76fef53ad497d [INFO] running `Command { std: "docker" "start" "-a" "7eb0e93be69ca8d6138fcb4af7a77da21fa40afa2c0686f2a5b76fef53ad497d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "7eb0e93be69ca8d6138fcb4af7a77da21fa40afa2c0686f2a5b76fef53ad497d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7eb0e93be69ca8d6138fcb4af7a77da21fa40afa2c0686f2a5b76fef53ad497d", kill_on_drop: false }` [INFO] [stdout] 7eb0e93be69ca8d6138fcb4af7a77da21fa40afa2c0686f2a5b76fef53ad497d [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+23718020b12d7e5a54f82a19910e8356ee719667" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 8cac65bd02f5587ca7c1c18e8e905f9abef3a21a5d396b72078b8b3d99130bb7 [INFO] running `Command { std: "docker" "start" "-a" "8cac65bd02f5587ca7c1c18e8e905f9abef3a21a5d396b72078b8b3d99130bb7", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.79 [INFO] [stderr] Compiling libc v0.2.153 [INFO] [stderr] Compiling autocfg v1.2.0 [INFO] [stderr] Compiling serde v1.0.200 [INFO] [stderr] Checking memchr v2.7.2 [INFO] [stderr] Checking log v0.4.21 [INFO] [stderr] Checking bytes v1.6.0 [INFO] [stderr] Checking bitflags v2.5.0 [INFO] [stderr] Checking ryu v1.0.17 [INFO] [stderr] Compiling rustix v0.38.32 [INFO] [stderr] Checking futures-io v0.3.30 [INFO] [stderr] Compiling serde_json v1.0.116 [INFO] [stderr] Checking regex-syntax v0.8.3 [INFO] [stderr] Checking hashbrown v0.14.3 [INFO] [stderr] Checking linux-raw-sys v0.4.13 [INFO] [stderr] Checking aho-corasick v1.1.3 [INFO] [stderr] Compiling thiserror v1.0.59 [INFO] [stderr] Compiling quote v1.0.36 [INFO] [stderr] Checking unicode-bidi v0.3.15 [INFO] [stderr] Checking miniz_oxide v0.7.2 [INFO] [stderr] Compiling syn v2.0.58 [INFO] [stderr] Compiling jobserver v0.1.28 [INFO] [stderr] Checking tinyvec v1.6.0 [INFO] [stderr] Compiling slab v0.4.9 [INFO] [stderr] Compiling cc v1.0.92 [INFO] [stderr] Checking getrandom v0.2.14 [INFO] [stderr] Checking mio v0.8.11 [INFO] [stderr] Checking num_cpus v1.16.0 [INFO] [stderr] Checking signal-hook-registry v1.4.1 [INFO] [stderr] Checking socket2 v0.5.6 [INFO] [stderr] Checking utf8parse v0.2.1 [INFO] [stderr] Compiling crc32fast v1.4.0 [INFO] [stderr] Compiling num-traits v0.2.18 [INFO] [stderr] Checking subtle v2.5.0 [INFO] [stderr] Checking regex-automata v0.4.6 [INFO] [stderr] Checking anstyle v1.0.6 [INFO] [stderr] Compiling crossbeam-utils v0.8.19 [INFO] [stderr] Checking unicode-normalization v0.1.23 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Checking http v1.1.0 [INFO] [stderr] Compiling cmake v0.1.50 [INFO] [stderr] Checking idna v0.5.0 [INFO] [stderr] Checking rustls-pki-types v1.4.1 [INFO] [stderr] Compiling libz-ng-sys v1.1.15 [INFO] [stderr] Compiling ring v0.17.8 [INFO] [stderr] Compiling zstd-sys v2.0.10+zstd.1.5.6 [INFO] [stderr] Checking anstyle-parse v0.2.3 [INFO] [stderr] Compiling httparse v1.8.0 [INFO] [stderr] Checking colorchoice v1.0.0 [INFO] [stderr] Checking anstyle-query v1.0.2 [INFO] [stderr] Checking is_terminal_polyfill v1.70.0 [INFO] [stderr] Checking http-body v1.0.0 [INFO] [stderr] Checking anstream v0.6.14 [INFO] [stderr] Compiling bzip2-sys v0.1.11+1.0.8 [INFO] [stderr] Checking unicode-width v0.1.12 [INFO] [stderr] Compiling zstd-safe v7.1.0 [INFO] [stderr] Checking regex v1.10.4 [INFO] [stderr] Compiling generic-array v0.14.7 [INFO] [stderr] Compiling anyhow v1.0.82 [INFO] [stderr] Compiling rustls v0.22.3 [INFO] [stderr] Checking brotli-decompressor v4.0.0 [INFO] [stderr] Checking fastrand v2.0.2 [INFO] [stderr] Checking seahash v4.1.0 [INFO] [stderr] Checking zeroize v1.7.0 [INFO] [stderr] Checking bzip2 v0.4.4 [INFO] [stderr] Compiling openssl-src v300.2.3+3.2.1 [INFO] [stderr] Checking brotli v5.0.0 [INFO] [stderr] Checking rand_core v0.6.4 [INFO] [stderr] Compiling ahash v0.7.8 [INFO] [stderr] Compiling bytecheck v0.6.12 [INFO] [stderr] Checking rustls-pemfile v2.1.2 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Compiling openssl-sys v0.9.102 [INFO] [stderr] Compiling libz-sys v1.1.16 [INFO] [stderr] Checking http-body-util v0.1.1 [INFO] [stderr] Checking crossbeam-epoch v0.9.18 [INFO] [stderr] Checking simdutf8 v0.1.4 [INFO] [stderr] Compiling rend v0.4.2 [INFO] [stderr] Checking crossbeam-deque v0.8.5 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Compiling serde_derive v1.0.200 [INFO] [stderr] Compiling tokio-macros v2.2.0 [INFO] [stderr] Compiling tracing-attributes v0.1.27 [INFO] [stderr] Checking tokio v1.37.0 [INFO] [stderr] Compiling thiserror-impl v1.0.59 [INFO] [stderr] Checking tracing v0.1.40 [INFO] [stderr] Compiling futures-macro v0.3.30 [INFO] [stderr] Compiling pin-project-internal v1.1.5 [INFO] [stderr] Checking futures-util v0.3.30 [INFO] [stderr] Checking rustls-webpki v0.102.2 [INFO] [stderr] Checking pin-project v1.1.5 [INFO] [stderr] Compiling ptr_meta_derive v0.1.4 [INFO] [stderr] Checking ptr_meta v0.1.4 [INFO] [stderr] Compiling bytecheck_derive v0.6.12 [INFO] [stderr] Checking rustls-native-certs v0.7.0 [INFO] [stderr] Checking crypto-common v0.1.6 [INFO] [stderr] Checking block-buffer v0.10.4 [INFO] [stderr] Checking tempfile v3.10.1 [INFO] [stderr] Checking bstr v1.9.1 [INFO] [stderr] Checking tokio-util v0.7.11 [INFO] [stderr] Checking webpki-roots v0.26.1 [INFO] [stderr] Compiling rkyv v0.7.44 [INFO] [stderr] Checking tower v0.4.13 [INFO] [stderr] Checking tokio-rustls v0.25.0 [INFO] [stderr] Checking digest v0.10.7 [INFO] [stderr] Checking hashbrown v0.12.3 [INFO] [stderr] Compiling rkyv_derive v0.7.44 [INFO] [stderr] Compiling libssh2-sys v0.3.0 [INFO] [stderr] Compiling fs-err v2.11.0 [INFO] [stderr] Checking owo-colors v4.0.0 [INFO] [stderr] Checking indexmap v2.2.6 [INFO] [stderr] Checking url v2.5.0 [INFO] [stderr] Checking h2 v0.4.4 [INFO] [stderr] Checking serde_urlencoded v0.7.1 [INFO] [stderr] Checking globset v0.4.14 [INFO] [stderr] Checking zstd v0.13.1 [INFO] [stderr] Compiling serde_derive_internals v0.29.0 [INFO] [stderr] Checking urlencoding v2.1.3 [INFO] [stderr] Compiling schemars v0.8.17 [INFO] [stderr] Checking ignore v0.4.22 [INFO] [stderr] Compiling libgit2-sys v0.16.2+1.7.2 [INFO] [stderr] Checking path-dedot v3.1.1 [INFO] [stderr] Checking instant v0.1.12 [INFO] [stderr] Checking dyn-clone v1.0.17 [INFO] [stderr] Checking path-absolutize v3.1.1 [INFO] [stderr] Checking backoff v0.4.0 [INFO] [stderr] Checking uv-warnings v0.0.1 (/opt/rustwide/workdir/crates/uv-warnings) [INFO] [stderr] Checking encoding_rs_io v0.1.7 [INFO] [stderr] Checking cachedir v0.3.1 [INFO] [stderr] Checking filetime v0.2.23 [INFO] [stderr] Checking fs2 v0.4.3 [INFO] [stderr] Checking dunce v1.0.4 [INFO] [stderr] Checking unscanny v0.1.0 [INFO] [stderr] Compiling schemars_derive v0.8.17 [INFO] [stderr] Checking sha2 v0.10.8 [INFO] [stderr] Checking shell-escape v0.1.5 [INFO] [stderr] Checking home v0.5.9 [INFO] [stderr] Checking uv-fs v0.0.1 (/opt/rustwide/workdir/crates/uv-fs) [INFO] [stderr] Checking sha1 v0.10.6 [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-fs/src/lib.rs:298:17 [INFO] [stdout] | [INFO] [stdout] 298 | / warn_user!( [INFO] [stdout] 299 | | "Waiting to acquire lock for {} (lockfile: {})", [INFO] [stdout] 300 | | resource, [INFO] [stdout] 301 | | path.user_display(), [INFO] [stdout] 302 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `tokio` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking cache-key v0.0.1 (/opt/rustwide/workdir/crates/cache-key) [INFO] [stderr] Checking cargo-util v0.2.11 [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:28:27 [INFO] [stdout] | [INFO] [stdout] 28 | fn simplified_display(&self) -> std::path::Display; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | fn simplified_display(&self) -> std::path::Display<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:36:21 [INFO] [stdout] | [INFO] [stdout] 36 | fn user_display(&self) -> std::path::Display; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 36 | fn user_display(&self) -> std::path::Display<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:44:27 [INFO] [stdout] | [INFO] [stdout] 44 | fn simplified_display(&self) -> std::path::Display { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 44 | fn simplified_display(&self) -> std::path::Display<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | fn user_display(&self) -> std::path::Display { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 52 | fn user_display(&self) -> std::path::Display<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:154:30 [INFO] [stdout] | [INFO] [stdout] 154 | pub fn absolutize_path(path: &Path) -> Result, std::io::Error> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 154 | pub fn absolutize_path(path: &Path) -> Result, std::io::Error> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking hmac v0.12.1 [INFO] [stderr] Checking glob v0.3.1 [INFO] [stderr] Checking either v1.11.0 [INFO] [stderr] Checking chrono v0.4.38 [INFO] [stderr] Checking toml_datetime v0.6.5 [INFO] [stderr] Checking serde_spanned v0.6.5 [INFO] [stderr] Compiling derivative v2.2.0 [INFO] [stderr] Checking terminal_size v0.3.0 [INFO] [stderr] Checking winnow v0.6.5 [INFO] [stderr] Checking charset v0.1.3 [INFO] [stderr] Checking clap_lex v0.7.0 [INFO] [stderr] Checking quoted_printable v0.5.0 [INFO] [stderr] Compiling clap_derive v4.5.4 [INFO] [stderr] Checking hyper v1.3.1 [INFO] [stderr] Checking clap_builder v4.5.2 [INFO] [stderr] Checking toml_edit v0.22.9 [INFO] [stderr] Checking mailparse v0.15.0 [INFO] [stderr] Checking futures-executor v0.3.30 [INFO] [stderr] Checking futures v0.3.30 [INFO] [stderr] Checking platform-tags v0.0.1 (/opt/rustwide/workdir/crates/platform-tags) [INFO] [stderr] Checking pep440_rs v0.5.0 (/opt/rustwide/workdir/crates/pep440-rs) [INFO] [stderr] Checking hyper-util v0.1.3 [INFO] [stderr] Checking uv-normalize v0.0.1 (/opt/rustwide/workdir/crates/uv-normalize) [INFO] [stderr] Compiling async-trait v0.1.80 [INFO] [stderr] Checking flate2 v1.0.30 [INFO] [stderr] Compiling lock_api v0.4.11 [INFO] [stderr] Checking clap v4.5.4 [INFO] [stderr] Checking hyper-rustls v0.26.0 [INFO] [stderr] Checking toml v0.8.12 [INFO] [stderr] Compiling parking_lot_core v0.9.9 [INFO] [stderr] Checking distribution-filename v0.0.1 (/opt/rustwide/workdir/crates/distribution-filename) [INFO] [stderr] Checking async-compression v0.4.9 [INFO] [stderr] Checking itertools v0.12.1 [INFO] [stderr] Compiling paste v1.0.14 [INFO] [stderr] Checking parking v2.2.0 [INFO] [stderr] Compiling zip v1.1.4 [INFO] [stderr] Checking option-ext v0.2.0 [INFO] [stderr] Checking dirs-sys v0.4.1 [INFO] [stderr] Compiling displaydoc v0.2.4 [INFO] [stderr] Checking directories v5.0.1 [INFO] [stderr] Checking dashmap v5.5.3 [INFO] [stderr] Checking tokio-stream v0.1.15 [INFO] [stderr] Compiling toml_edit v0.21.1 [INFO] [stderr] Checking rmp v0.8.14 [INFO] [stderr] Checking once-map v0.0.1 (/opt/rustwide/workdir/crates/once-map) [INFO] [stderr] Checking rmp-serde v1.3.0 [INFO] [stderr] Checking rust-netrc v0.1.1 [INFO] [stderr] Checking nanoid v0.4.0 [INFO] [stderr] Checking futures-lite v2.3.0 [INFO] [stderr] Checking csv-core v0.1.11 [INFO] [stderr] Compiling sys-info v0.9.1 [INFO] [stderr] Checking reflink-copy v0.1.17 [INFO] [stderr] Checking csv v1.3.0 [INFO] [stderr] Checking reqwest v0.12.4 [INFO] [stderr] Checking platform-info v2.0.3 [INFO] [stderr] Checking pathdiff v0.2.1 [INFO] [stderr] Checking configparser v3.0.4 [INFO] [stderr] Checking retry-policies v0.3.0 [INFO] [stderr] Checking memmap2 v0.9.4 [INFO] [stderr] Checking http-content-range v0.1.2 [INFO] [stderr] Checking bisection v0.1.0 [INFO] [stderr] Checking utf8-width v0.1.7 [INFO] [stderr] Checking uv-version v0.1.41 (/opt/rustwide/workdir/crates/uv-version) [INFO] [stderr] Checking html-escape v0.2.13 [INFO] [stderr] Checking tl v0.7.8 [INFO] [stderr] Checking rayon-core v1.12.1 [INFO] [stderr] Checking xattr v1.3.1 [INFO] [stderr] Checking async_zip v0.0.17 (https://github.com/charliermarsh/rs-async-zip?rev=1dcb40cfe1bf5325a6fd4bfcf9894db40241f585#1dcb40cf) [INFO] [stderr] Checking tokio-tar v0.3.1 [INFO] [stderr] Checking md-5 v0.10.6 [INFO] [stderr] Checking reqwest-middleware v0.3.0 [INFO] [stderr] Checking rayon v1.10.0 [INFO] [stderr] Checking lazy_static v1.4.0 [INFO] [stderr] Checking which v6.0.1 [INFO] [stderr] Checking console v0.15.8 [INFO] [stderr] Checking smawk v0.3.2 [INFO] [stderr] Checking uv-auth v0.0.1 (/opt/rustwide/workdir/crates/uv-auth) [INFO] [stderr] Checking async_http_range_reader v0.8.0 [INFO] [stderr] Checking reqwest-retry v0.5.0 [INFO] [stderr] Checking textwrap v0.16.1 [INFO] [stderr] Checking priority-queue v2.0.2 [INFO] [stderr] Compiling proc-macro-crate v3.1.0 [INFO] [stderr] Checking petgraph v0.6.4 [INFO] [stderr] Compiling ucd-trie v0.1.6 [INFO] [stderr] Checking pubgrub v0.2.1 (https://github.com/astral-sh/pubgrub?rev=0e684a874c9fb8f74738cd8875524c80e3d4820b#0e684a87) [INFO] [stderr] Checking linked-hash-map v0.5.6 [INFO] [stderr] Checking pest v2.7.8 [INFO] [stderr] Checking similar v2.5.0 [INFO] [stderr] Checking float-cmp v0.9.0 [INFO] [stderr] Compiling nix v0.28.0 [INFO] [stderr] Compiling indoc v2.0.5 [INFO] [stderr] Checking concurrent-queue v2.4.0 [INFO] [stderr] Compiling num_enum_derive v0.7.2 [INFO] [stderr] Checking event-listener v5.3.0 [INFO] [stderr] Checking sharded-slab v0.1.7 [INFO] [stderr] Checking tracing-serde v0.1.3 [INFO] [stderr] Checking tracing-log v0.2.0 [INFO] [stderr] Checking event-listener-strategy v0.5.1 [INFO] [stderr] Compiling vte_generate_state_changes v0.1.1 [INFO] [stderr] Compiling portable-atomic v1.6.0 [INFO] [stderr] Checking async-channel v2.2.1 [INFO] [stderr] Checking vte v0.11.1 [INFO] [stderr] Compiling tikv-jemalloc-sys v0.5.4+5.3.0-patched [INFO] [stderr] Checking num_enum v0.7.2 [INFO] [stderr] Checking tracing-subscriber v0.3.18 [INFO] [stderr] Checking ctrlc v3.4.4 [INFO] [stderr] Compiling backtrace v0.3.71 [INFO] [stderr] Compiling pest_meta v2.7.8 [INFO] [stderr] Compiling doc-comment v0.3.3 [INFO] [stderr] Checking predicates-core v1.0.6 [INFO] [stderr] Checking gimli v0.28.1 [INFO] [stderr] Checking vt100 v0.15.2 [INFO] [stderr] Checking clap_complete v4.5.2 [INFO] [stderr] Checking object v0.32.2 [INFO] [stderr] Checking rustc-demangle v0.1.23 [INFO] [stderr] Checking indicatif v0.17.8 [INFO] [stderr] Compiling pest_generator v2.7.8 [INFO] [stderr] Checking normalize-line-endings v0.3.0 [INFO] [stderr] Checking difflib v0.4.0 [INFO] [stderr] Checking termtree v0.4.1 [INFO] [stderr] Checking predicates v3.1.0 [INFO] [stderr] Checking predicates-tree v1.0.9 [INFO] [stderr] Checking is_ci v1.2.0 [INFO] [stderr] Compiling uv v0.1.41 (/opt/rustwide/workdir/crates/uv) [INFO] [stderr] Checking supports-color v3.0.0 [INFO] [stderr] Checking clap_complete_fig v4.5.0 [INFO] [stderr] Compiling pest_derive v2.7.8 [INFO] [stderr] Checking clap_complete_nushell v0.1.11 [INFO] [stderr] Checking globwalk v0.9.1 [INFO] [stderr] Compiling miette-derive v7.2.0 [INFO] [stderr] Compiling assert_cmd v2.0.14 [INFO] [stderr] Checking nu-ansi-term v0.49.0 [INFO] [stderr] Checking insta v1.38.0 [INFO] [stderr] Checking supports-hyperlinks v3.0.0 [INFO] [stderr] Checking supports-unicode v3.0.0 [INFO] [stderr] Checking assert_fs v1.1.1 [INFO] [stderr] Checking tracing-tree v0.3.0 [INFO] [stderr] Checking clap_complete_command v0.5.1 [INFO] [stderr] Checking wait-timeout v0.2.0 [INFO] [stderr] Checking bytemuck v1.15.0 [INFO] [stderr] Checking addr2line v0.21.0 [INFO] [stderr] Checking strict-num v0.1.1 [INFO] [stderr] Checking kurbo v0.8.3 [INFO] [stderr] Checking half v2.4.1 [INFO] [stderr] Checking xmlparser v0.13.6 [INFO] [stderr] Checking ciborium-io v0.2.2 [INFO] [stderr] Compiling unicode-general-category v0.6.0 [INFO] [stderr] Checking ciborium-ll v0.2.2 [INFO] [stderr] Checking kurbo v0.9.5 [INFO] [stderr] Checking itertools v0.10.5 [INFO] [stderr] Checking roxmltree v0.18.1 [INFO] [stderr] Checking svgtypes v0.9.0 [INFO] [stderr] Checking simplecss v0.2.1 [INFO] [stderr] Checking cast v0.3.0 [INFO] [stderr] Checking ttf-parser v0.18.1 [INFO] [stderr] Checking roxmltree v0.19.0 [INFO] [stderr] Checking rosvgtree v0.1.0 [INFO] [stderr] Checking fontconfig-parser v0.5.6 [INFO] [stderr] Checking ciborium v0.2.2 [INFO] [stderr] Checking backtrace-ext v0.2.1 [INFO] [stderr] Checking miette v7.2.0 [INFO] [stderr] Checking tinytemplate v1.2.1 [INFO] [stderr] Checking criterion-plot v0.5.0 [INFO] [stderr] Checking is-terminal v0.4.12 [INFO] [stderr] Checking memmap2 v0.5.10 [INFO] [stderr] Checking fdeflate v0.3.4 [INFO] [stderr] Checking data-url v0.2.0 [INFO] [stderr] Checking anes v0.1.6 [INFO] [stderr] Checking arrayref v0.3.7 [INFO] [stderr] Checking unicode-script v0.5.6 [INFO] [stderr] Checking unicode-ccc v0.1.2 [INFO] [stderr] Checking imagesize v0.11.0 [INFO] [stderr] Checking rctree v0.5.0 [INFO] [stderr] Checking unicode-bidi-mirroring v0.1.0 [INFO] [stderr] Checking oorandom v11.1.3 [INFO] [stderr] Checking png v0.17.13 [INFO] [stderr] Checking usvg v0.29.0 [INFO] [stderr] Checking criterion v0.5.1 [INFO] [stderr] Checking tiny-skia-path v0.8.4 [INFO] [stderr] Checking rgb v0.8.37 [INFO] [stderr] Checking unicode-vo v0.1.0 [INFO] [stderr] Checking weezl v0.1.8 [INFO] [stderr] Checking color_quant v1.1.0 [INFO] [stderr] Checking tiny-skia v0.8.4 [INFO] [stderr] Compiling test-case-core v3.3.1 [INFO] [stderr] Checking svgfilters v0.4.0 [INFO] [stderr] Checking gif v0.12.0 [INFO] [stderr] Checking svgtypes v0.10.0 [INFO] [stderr] Checking yansi v0.5.1 [INFO] [stderr] Checking rustybuzz v0.7.0 [INFO] [stderr] Checking fontdb v0.12.0 [INFO] [stderr] Checking diff v0.1.13 [INFO] [stderr] Checking pico-args v0.5.0 [INFO] [stderr] Checking svg v0.15.1 [INFO] [stderr] Checking jpeg-decoder v0.3.1 [INFO] [stderr] Checking tagu v0.1.6 [INFO] [stderr] Checking deadpool-runtime v0.1.3 [INFO] [stderr] Checking deadpool v0.10.0 [INFO] [stderr] Checking poloto v19.1.2 [INFO] [stderr] Compiling test-case-macros v3.3.1 [INFO] [stderr] Checking pretty_assertions v1.4.0 [INFO] [stderr] Checking tracing-durations-export v0.2.0 [INFO] [stderr] Checking tracing-indicatif v0.3.6 [INFO] [stderr] Checking assert-json-diff v2.0.2 [INFO] [stderr] Compiling test-log-macros v0.2.15 [INFO] [stderr] Checking testing_logger v0.1.1 [INFO] [stderr] Checking test-case v3.3.1 [INFO] [stderr] Checking wiremock v0.6.0 [INFO] [stderr] Checking test-log v0.2.16 [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-fs/src/lib.rs:298:17 [INFO] [stdout] | [INFO] [stdout] 298 | / warn_user!( [INFO] [stdout] 299 | | "Waiting to acquire lock for {} (lockfile: {})", [INFO] [stdout] 300 | | resource, [INFO] [stdout] 301 | | path.user_display(), [INFO] [stdout] 302 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default` and `tokio` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:28:27 [INFO] [stdout] | [INFO] [stdout] 28 | fn simplified_display(&self) -> std::path::Display; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | fn simplified_display(&self) -> std::path::Display<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:36:21 [INFO] [stdout] | [INFO] [stdout] 36 | fn user_display(&self) -> std::path::Display; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 36 | fn user_display(&self) -> std::path::Display<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:44:27 [INFO] [stdout] | [INFO] [stdout] 44 | fn simplified_display(&self) -> std::path::Display { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 44 | fn simplified_display(&self) -> std::path::Display<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | fn user_display(&self) -> std::path::Display { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 52 | fn user_display(&self) -> std::path::Display<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-fs/src/path.rs:154:30 [INFO] [stdout] | [INFO] [stdout] 154 | pub fn absolutize_path(path: &Path) -> Result, std::io::Error> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 154 | pub fn absolutize_path(path: &Path) -> Result, std::io::Error> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking usvg-text-layout v0.29.0 [INFO] [stderr] Checking resvg v0.29.0 [INFO] [stderr] Checking tikv-jemallocator v0.5.4 [INFO] [stderr] Checking git2 v0.18.3 [INFO] [stderr] Checking uv-git v0.0.1 (/opt/rustwide/workdir/crates/uv-git) [INFO] [stderr] Checking pep508_rs v0.4.2 (/opt/rustwide/workdir/crates/pep508-rs) [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/pep508-rs/src/verbatim_url.rs:362:25 [INFO] [stdout] | [INFO] [stdout] 362 | fn split_fragment(path: &Path) -> (Cow, Option<&str>) { [INFO] [stdout] | ^^^^^ ^^^^^^^^^ ^^^^ the same lifetime is elided here [INFO] [stdout] | | | [INFO] [stdout] | | the same lifetime is hidden here [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 362 | fn split_fragment(path: &Path) -> (Cow<'_, Path>, Option<&str>) { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking pypi-types v0.0.1 (/opt/rustwide/workdir/crates/pypi-types) [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/pep508-rs/src/verbatim_url.rs:362:25 [INFO] [stdout] | [INFO] [stdout] 362 | fn split_fragment(path: &Path) -> (Cow, Option<&str>) { [INFO] [stdout] | ^^^^^ ^^^^^^^^^ ^^^^ the same lifetime is elided here [INFO] [stdout] | | | [INFO] [stdout] | | the same lifetime is hidden here [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 362 | fn split_fragment(path: &Path) -> (Cow<'_, Path>, Option<&str>) { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking distribution-types v0.0.1 (/opt/rustwide/workdir/crates/distribution-types) [INFO] [stderr] Checking install-wheel-rs v0.0.1 (/opt/rustwide/workdir/crates/install-wheel-rs) [INFO] [stderr] Checking uv-extract v0.0.1 (/opt/rustwide/workdir/crates/uv-extract) [INFO] [stdout] warning: unexpected `cfg` condition value: `unix` [INFO] [stdout] --> crates/uv-extract/src/tar.rs:6:16 [INFO] [stdout] | [INFO] [stdout] 6 | #[cfg_attr(not(target_os = "unix"), allow(dead_code))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `redox`, `rtems`, `solaris`, `solid_asp3`, `teeos`, `trusty`, and `tvos` and 11 more [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `unix` [INFO] [stdout] --> crates/uv-extract/src/tar.rs:6:16 [INFO] [stdout] | [INFO] [stdout] 6 | #[cfg_attr(not(target_os = "unix"), allow(dead_code))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `redox`, `rtems`, `solaris`, `solid_asp3`, `teeos`, `trusty`, and `tvos` and 11 more [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:577:23 [INFO] [stdout] | [INFO] [stdout] 577 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 577 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:583:23 [INFO] [stdout] | [INFO] [stdout] 583 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 583 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:589:23 [INFO] [stdout] | [INFO] [stdout] 589 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 589 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:595:23 [INFO] [stdout] | [INFO] [stdout] 595 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 595 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:601:23 [INFO] [stdout] | [INFO] [stdout] 601 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 601 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:607:23 [INFO] [stdout] | [INFO] [stdout] 607 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 607 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:613:23 [INFO] [stdout] | [INFO] [stdout] 613 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 613 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:619:23 [INFO] [stdout] | [INFO] [stdout] 619 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 619 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:630:23 [INFO] [stdout] | [INFO] [stdout] 630 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 630 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:640:23 [INFO] [stdout] | [INFO] [stdout] 640 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 640 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/any.rs:24:26 [INFO] [stdout] | [INFO] [stdout] 24 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 24 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:190:23 [INFO] [stdout] | [INFO] [stdout] 190 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 190 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:196:23 [INFO] [stdout] | [INFO] [stdout] 196 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 196 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:202:23 [INFO] [stdout] | [INFO] [stdout] 202 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 202 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:211:26 [INFO] [stdout] | [INFO] [stdout] 211 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 211 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:217:26 [INFO] [stdout] | [INFO] [stdout] 217 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 217 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:223:26 [INFO] [stdout] | [INFO] [stdout] 223 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 223 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:290:23 [INFO] [stdout] | [INFO] [stdout] 290 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 290 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:331:26 [INFO] [stdout] | [INFO] [stdout] 331 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 331 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:337:26 [INFO] [stdout] | [INFO] [stdout] 337 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 337 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:343:26 [INFO] [stdout] | [INFO] [stdout] 343 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 343 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:349:26 [INFO] [stdout] | [INFO] [stdout] 349 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 349 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:355:26 [INFO] [stdout] | [INFO] [stdout] 355 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 355 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/prioritized_distribution.rs:218:16 [INFO] [stdout] | [INFO] [stdout] 218 | pub fn get(&self) -> Option { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 218 | pub fn get(&self) -> Option> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/resolved.rs:72:23 [INFO] [stdout] | [INFO] [stdout] 72 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 72 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/resolved.rs:106:23 [INFO] [stdout] | [INFO] [stdout] 106 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 106 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/traits.rs:27:23 [INFO] [stdout] | [INFO] [stdout] 27 | fn version_or_url(&self) -> VersionOrUrlRef; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 27 | fn version_or_url(&self) -> VersionOrUrlRef<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/traits.rs:60:26 [INFO] [stdout] | [INFO] [stdout] 60 | fn installed_version(&self) -> InstalledVersion; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 60 | fn installed_version(&self) -> InstalledVersion<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:577:23 [INFO] [stdout] | [INFO] [stdout] 577 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 577 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:583:23 [INFO] [stdout] | [INFO] [stdout] 583 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 583 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:589:23 [INFO] [stdout] | [INFO] [stdout] 589 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 589 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:595:23 [INFO] [stdout] | [INFO] [stdout] 595 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 595 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:601:23 [INFO] [stdout] | [INFO] [stdout] 601 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 601 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:607:23 [INFO] [stdout] | [INFO] [stdout] 607 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 607 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:613:23 [INFO] [stdout] | [INFO] [stdout] 613 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 613 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:619:23 [INFO] [stdout] | [INFO] [stdout] 619 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 619 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:630:23 [INFO] [stdout] | [INFO] [stdout] 630 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 630 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/lib.rs:640:23 [INFO] [stdout] | [INFO] [stdout] 640 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 640 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/any.rs:24:26 [INFO] [stdout] | [INFO] [stdout] 24 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 24 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:190:23 [INFO] [stdout] | [INFO] [stdout] 190 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 190 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:196:23 [INFO] [stdout] | [INFO] [stdout] 196 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 196 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:202:23 [INFO] [stdout] | [INFO] [stdout] 202 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 202 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:211:26 [INFO] [stdout] | [INFO] [stdout] 211 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 211 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:217:26 [INFO] [stdout] | [INFO] [stdout] 217 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 217 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/cached.rs:223:26 [INFO] [stdout] | [INFO] [stdout] 223 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 223 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:290:23 [INFO] [stdout] | [INFO] [stdout] 290 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 290 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:331:26 [INFO] [stdout] | [INFO] [stdout] 331 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 331 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:337:26 [INFO] [stdout] | [INFO] [stdout] 337 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 337 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:343:26 [INFO] [stdout] | [INFO] [stdout] 343 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 343 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:349:26 [INFO] [stdout] | [INFO] [stdout] 349 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 349 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/installed.rs:355:26 [INFO] [stdout] | [INFO] [stdout] 355 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 355 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/prioritized_distribution.rs:218:16 [INFO] [stdout] | [INFO] [stdout] 218 | pub fn get(&self) -> Option { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 218 | pub fn get(&self) -> Option> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/resolved.rs:72:23 [INFO] [stdout] | [INFO] [stdout] 72 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 72 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/resolved.rs:106:23 [INFO] [stdout] | [INFO] [stdout] 106 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 106 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/traits.rs:27:23 [INFO] [stdout] | [INFO] [stdout] 27 | fn version_or_url(&self) -> VersionOrUrlRef; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 27 | fn version_or_url(&self) -> VersionOrUrlRef<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/distribution-types/src/traits.rs:60:26 [INFO] [stdout] | [INFO] [stdout] 60 | fn installed_version(&self) -> InstalledVersion; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 60 | fn installed_version(&self) -> InstalledVersion<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-cache v0.0.1 (/opt/rustwide/workdir/crates/uv-cache) [INFO] [stderr] Checking uv-configuration v0.0.1 (/opt/rustwide/workdir/crates/uv-configuration) [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-configuration/src/constraints.rs:40:31 [INFO] [stdout] | [INFO] [stdout] 38 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 39 | requirements: impl IntoIterator, [INFO] [stdout] 40 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 40 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-configuration/src/overrides.rs:41:31 [INFO] [stdout] | [INFO] [stdout] 39 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 40 | requirements: impl IntoIterator, [INFO] [stdout] 41 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 41 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-configuration/src/constraints.rs:40:31 [INFO] [stdout] | [INFO] [stdout] 38 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 39 | requirements: impl IntoIterator, [INFO] [stdout] 40 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 40 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-configuration/src/overrides.rs:41:31 [INFO] [stdout] | [INFO] [stdout] 39 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 40 | requirements: impl IntoIterator, [INFO] [stdout] 41 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 41 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-client v0.0.1 (/opt/rustwide/workdir/crates/uv-client) [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-client/src/base_client.rs:123:25 [INFO] [stdout] | [INFO] [stdout] 123 | ... warn_user_once!("Ignoring invalid value from environment for UV_HTTP_TIMEOUT. Expected integer number of seconds, got \"{value}\"."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-client/src/base_client.rs:136:21 [INFO] [stdout] | [INFO] [stdout] 136 | / warn_user_once!( [INFO] [stdout] 137 | | "Ignoring invalid `SSL_CERT_FILE`. File does not exist: {}.", [INFO] [stdout] 138 | | path.simplified_display() [INFO] [stdout] 139 | | ); [INFO] [stdout] | |_____________________^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-client/src/base_client.rs:123:25 [INFO] [stdout] | [INFO] [stdout] 123 | ... warn_user_once!("Ignoring invalid value from environment for UV_HTTP_TIMEOUT. Expected integer number of seconds, got \"{value}\"."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-client/src/base_client.rs:136:21 [INFO] [stdout] | [INFO] [stdout] 136 | / warn_user_once!( [INFO] [stdout] 137 | | "Ignoring invalid `SSL_CERT_FILE`. File does not exist: {}.", [INFO] [stdout] 138 | | path.simplified_display() [INFO] [stdout] 139 | | ); [INFO] [stdout] | |_____________________^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-interpreter v0.0.1 (/opt/rustwide/workdir/crates/uv-interpreter) [INFO] [stderr] Checking requirements-txt v0.0.1 (/opt/rustwide/workdir/crates/requirements-txt) [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/requirements-txt/src/lib.rs:430:13 [INFO] [stdout] | [INFO] [stdout] 430 | / warn_user!( [INFO] [stdout] 431 | | "Requirements file {} does not contain any dependencies", [INFO] [stdout] 432 | | requirements_txt.user_display() [INFO] [stdout] 433 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `http`, `reqwest`, and `reqwest-middleware` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/requirements-txt/src/lib.rs:430:13 [INFO] [stdout] | [INFO] [stdout] 430 | / warn_user!( [INFO] [stdout] 431 | | "Requirements file {} does not contain any dependencies", [INFO] [stdout] 432 | | requirements_txt.user_display() [INFO] [stdout] 433 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `http`, `reqwest`, and `reqwest-middleware` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-interpreter/src/find_python.rs:417:9 [INFO] [stdout] | [INFO] [stdout] 417 | / warn_user_once!( [INFO] [stdout] 418 | | "uv is only compatible with Python 3.8+, found Python {}.", [INFO] [stdout] 419 | | interpreter.python_version() [INFO] [stdout] 420 | | ); [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-interpreter/src/find_python.rs:417:9 [INFO] [stdout] | [INFO] [stdout] 417 | / warn_user_once!( [INFO] [stdout] 418 | | "uv is only compatible with Python 3.8+, found Python {}.", [INFO] [stdout] 419 | | interpreter.python_version() [INFO] [stdout] 420 | | ); [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-types v0.0.1 (/opt/rustwide/workdir/crates/uv-types) [INFO] [stderr] Checking uv-virtualenv v0.0.4 (/opt/rustwide/workdir/crates/uv-virtualenv) [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/hash.rs:28:41 [INFO] [stdout] | [INFO] [stdout] 28 | pub fn get(&self, distribution: &T) -> HashPolicy { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | pub fn get(&self, distribution: &T) -> HashPolicy<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/hash.rs:42:24 [INFO] [stdout] | [INFO] [stdout] 42 | pub fn get_package(&self, name: &PackageName) -> HashPolicy { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 42 | pub fn get_package(&self, name: &PackageName) -> HashPolicy<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/hash.rs:56:20 [INFO] [stdout] | [INFO] [stdout] 56 | pub fn get_url(&self, url: &Url) -> HashPolicy { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 56 | pub fn get_url(&self, url: &Url) -> HashPolicy<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/traits.rs:62:24 [INFO] [stdout] | [INFO] [stdout] 62 | fn build_isolation(&self) -> BuildIsolation; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 62 | fn build_isolation(&self) -> BuildIsolation<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-distribution v0.0.1 (/opt/rustwide/workdir/crates/uv-distribution) [INFO] [stderr] Checking uv-build v0.0.1 (/opt/rustwide/workdir/crates/uv-build) [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/hash.rs:28:41 [INFO] [stdout] | [INFO] [stdout] 28 | pub fn get(&self, distribution: &T) -> HashPolicy { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | pub fn get(&self, distribution: &T) -> HashPolicy<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/hash.rs:42:24 [INFO] [stdout] | [INFO] [stdout] 42 | pub fn get_package(&self, name: &PackageName) -> HashPolicy { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 42 | pub fn get_package(&self, name: &PackageName) -> HashPolicy<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/hash.rs:56:20 [INFO] [stdout] | [INFO] [stdout] 56 | pub fn get_url(&self, url: &Url) -> HashPolicy { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 56 | pub fn get_url(&self, url: &Url) -> HashPolicy<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-types/src/traits.rs:62:24 [INFO] [stdout] | [INFO] [stdout] 62 | fn build_isolation(&self) -> BuildIsolation; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 62 | fn build_isolation(&self) -> BuildIsolation<'_>; [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-resolver v0.0.1 (/opt/rustwide/workdir/crates/uv-resolver) [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-resolver/src/version_map.rs:371:29 [INFO] [stdout] | [INFO] [stdout] 371 | / ... warn_user_once!( [INFO] [stdout] 372 | | ... "{} is missing an upload date, but user provided: {exclude_newer}", [INFO] [stdout] 373 | | ... file.filename, [INFO] [stdout] 374 | | ... ); [INFO] [stdout] | |_______________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `clap`, `default`, `pypi`, and `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-resolver/src/version_map.rs:371:29 [INFO] [stdout] | [INFO] [stdout] 371 | / ... warn_user_once!( [INFO] [stdout] 372 | | ... "{} is missing an upload date, but user provided: {exclude_newer}", [INFO] [stdout] 373 | | ... file.filename, [INFO] [stdout] 374 | | ... ); [INFO] [stdout] | |_______________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `clap`, `default`, `pypi`, and `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: impl trait in impl method signature does not match trait method signature [INFO] [stdout] --> crates/uv-resolver/src/dependency_provider.rs:40:10 [INFO] [stdout] | [INFO] [stdout] 40 | ) -> Result, Self::M>, Self::Err> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: add `#[allow(refining_impl_trait)]` if it is intended for this to be part of the public API of this crate [INFO] [stdout] = note: we are soliciting feedback, see issue #121718 for more information [INFO] [stdout] = note: `#[warn(refining_impl_trait_internal)]` (part of `#[warn(refining_impl_trait)]`) on by default [INFO] [stdout] = note: the full name for the type has been written to '/opt/rustwide/target/debug/deps/uv_resolver-5fdc04bdd37cbf0a.long-type-3654409208440564163.txt' [INFO] [stdout] = note: consider using `--verbose` to print the full type name to the console [INFO] [stdout] help: replace the return type so that it matches the trait [INFO] [stdout] | [INFO] [stdout] 40 - ) -> Result, Self::M>, Self::Err> { [INFO] [stdout] 40 + ) -> Result::P, ::VS)> + std::clone::Clone, ::M>, ::Err> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: impl trait in impl method signature does not match trait method signature [INFO] [stdout] --> crates/uv-resolver/src/dependency_provider.rs:40:10 [INFO] [stdout] | [INFO] [stdout] 40 | ) -> Result, Self::M>, Self::Err> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: add `#[allow(refining_impl_trait)]` if it is intended for this to be part of the public API of this crate [INFO] [stdout] = note: we are soliciting feedback, see issue #121718 for more information [INFO] [stdout] = note: `#[warn(refining_impl_trait_internal)]` (part of `#[warn(refining_impl_trait)]`) on by default [INFO] [stdout] = note: the full name for the type has been written to '/opt/rustwide/target/debug/deps/uv_resolver-9e80c629527c7355.long-type-11435006644306208274.txt' [INFO] [stdout] = note: consider using `--verbose` to print the full type name to the console [INFO] [stdout] help: replace the return type so that it matches the trait [INFO] [stdout] | [INFO] [stdout] 40 - ) -> Result, Self::M>, Self::Err> { [INFO] [stdout] 40 + ) -> Result::P, ::VS)> + std::clone::Clone, ::M>, ::Err> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `#[must_use]` attribute cannot be used on trait methods in impl blocks [INFO] [stdout] --> crates/uv-resolver/src/resolver/provider.rs:218:5 [INFO] [stdout] | [INFO] [stdout] 218 | #[must_use] [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = help: `#[must_use]` can be applied to data types, functions, unions, required trait methods, provided trait methods, inherent methods, foreign functions, and traits [INFO] [stdout] = note: `#[warn(unused_attributes)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: `#[must_use]` attribute cannot be used on trait methods in impl blocks [INFO] [stdout] --> crates/uv-resolver/src/resolver/provider.rs:218:5 [INFO] [stdout] | [INFO] [stdout] 218 | #[must_use] [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! [INFO] [stdout] = help: `#[must_use]` can be applied to data types, functions, unions, required trait methods, provided trait methods, inherent methods, foreign functions, and traits [INFO] [stdout] = note: `#[warn(unused_attributes)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/candidate_selector.rs:214:17 [INFO] [stdout] | [INFO] [stdout] 210 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 211 | package_name: &'a PackageName, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 212 | range: &Range, [INFO] [stdout] 213 | version_maps: &'a [VersionMap], [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 214 | ) -> Option { [INFO] [stdout] | ^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 214 | ) -> Option> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/candidate_selector.rs:472:23 [INFO] [stdout] | [INFO] [stdout] 472 | fn version_or_url(&self) -> distribution_types::VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 472 | fn version_or_url(&self) -> distribution_types::VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/manifest.rs:102:31 [INFO] [stdout] | [INFO] [stdout] 99 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 100 | markers: &'a MarkerEnvironment, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 101 | mode: DependencyMode, [INFO] [stdout] 102 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 102 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/manifest.rs:162:31 [INFO] [stdout] | [INFO] [stdout] 159 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 160 | markers: &'a MarkerEnvironment, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 161 | mode: DependencyMode, [INFO] [stdout] 162 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 162 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/manifest.rs:211:31 [INFO] [stdout] | [INFO] [stdout] 209 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 210 | requirements: impl IntoIterator, [INFO] [stdout] 211 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 211 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/pubgrub/distribution.rs:32:23 [INFO] [stdout] | [INFO] [stdout] 32 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 32 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/version_map.rs:160:9 [INFO] [stdout] | [INFO] [stdout] 160 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] 161 | ) -> impl DoubleEndedIterator + ExactSizeIterator { [INFO] [stdout] | ^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 161 | ) -> impl DoubleEndedIterator)> + ExactSizeIterator { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-requirements v0.1.0 (/opt/rustwide/workdir/crates/uv-requirements) [INFO] [stderr] Checking uv-workspace v0.0.1 (/opt/rustwide/workdir/crates/uv-workspace) [INFO] [stderr] Checking bench v0.0.0 (/opt/rustwide/workdir/crates/bench) [INFO] [stdout] warning: hiding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/candidate_selector.rs:214:17 [INFO] [stdout] | [INFO] [stdout] 210 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 211 | package_name: &'a PackageName, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 212 | range: &Range, [INFO] [stdout] 213 | version_maps: &'a [VersionMap], [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 214 | ) -> Option { [INFO] [stdout] | ^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 214 | ) -> Option> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/candidate_selector.rs:472:23 [INFO] [stdout] | [INFO] [stdout] 472 | fn version_or_url(&self) -> distribution_types::VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 472 | fn version_or_url(&self) -> distribution_types::VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `codspeed` [INFO] [stdout] --> crates/bench/src/lib.rs:5:15 [INFO] [stdout] | [INFO] [stdout] 5 | #[cfg(not(codspeed))] [INFO] [stdout] | ^^^^^^^^ help: found config with similar value: `feature = "codspeed"` [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(codspeed)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(codspeed)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `codspeed` [INFO] [stdout] --> crates/bench/src/lib.rs:8:11 [INFO] [stdout] | [INFO] [stdout] 8 | #[cfg(codspeed)] [INFO] [stdout] | ^^^^^^^^ help: found config with similar value: `feature = "codspeed"` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(codspeed)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(codspeed)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/manifest.rs:102:31 [INFO] [stdout] | [INFO] [stdout] 99 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 100 | markers: &'a MarkerEnvironment, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 101 | mode: DependencyMode, [INFO] [stdout] 102 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 102 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/manifest.rs:162:31 [INFO] [stdout] | [INFO] [stdout] 159 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 160 | markers: &'a MarkerEnvironment, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 161 | mode: DependencyMode, [INFO] [stdout] 162 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 162 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/manifest.rs:211:31 [INFO] [stdout] | [INFO] [stdout] 209 | &'a self, [INFO] [stdout] | -- the lifetime is named here [INFO] [stdout] 210 | requirements: impl IntoIterator, [INFO] [stdout] 211 | ) -> impl Iterator { [INFO] [stdout] | ^^^^^^^^^^^^ the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 211 | ) -> impl Iterator { [INFO] [stdout] | ++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/pubgrub/distribution.rs:32:23 [INFO] [stdout] | [INFO] [stdout] 32 | fn version_or_url(&self) -> VersionOrUrlRef { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 32 | fn version_or_url(&self) -> VersionOrUrlRef<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `codspeed` [INFO] [stdout] --> crates/bench/src/lib.rs:5:15 [INFO] [stdout] | [INFO] [stdout] 5 | #[cfg(not(codspeed))] [INFO] [stdout] | ^^^^^^^^ help: found config with similar value: `feature = "codspeed"` [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(codspeed)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(codspeed)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `codspeed` [INFO] [stdout] --> crates/bench/src/lib.rs:8:11 [INFO] [stdout] | [INFO] [stdout] 8 | #[cfg(codspeed)] [INFO] [stdout] | ^^^^^^^^ help: found config with similar value: `feature = "codspeed"` [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(codspeed)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(codspeed)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/src/version_map.rs:160:9 [INFO] [stdout] | [INFO] [stdout] 160 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] 161 | ) -> impl DoubleEndedIterator + ExactSizeIterator { [INFO] [stdout] | ^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the same lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 161 | ) -> impl DoubleEndedIterator)> + ExactSizeIterator { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/pyproject.rs:413:13 [INFO] [stdout] | [INFO] [stdout] 413 | / warn_user_once!( [INFO] [stdout] 414 | | "Missing version constraint (e.g., a lower bound) for `{}`", [INFO] [stdout] 415 | | requirement.name [INFO] [stdout] 416 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/pyproject.rs:499:17 [INFO] [stdout] | [INFO] [stdout] 499 | / warn_user_once!( [INFO] [stdout] 500 | | "Missing version constraint (e.g., a lower bound) for `{}`", [INFO] [stdout] 501 | | requirement.name [INFO] [stdout] 502 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/sources.rs:46:17 [INFO] [stdout] | [INFO] [stdout] 46 | / warn_user!( [INFO] [stdout] 47 | | "The file `{}` appears to be a `{}` file, but requirements must be specified in `requirements.txt` format.", [INFO] [stdout] 48 | | path.user_display(), [INFO] [stdout] 49 | | filename [INFO] [stdout] 50 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/sources.rs:60:17 [INFO] [stdout] | [INFO] [stdout] 60 | / warn_user!( [INFO] [stdout] 61 | | "The file `{}` appears to be a `{}` file, but constraints must be specified in `requirements.txt` format.", [INFO] [stdout] 62 | | path.user_display(), [INFO] [stdout] 63 | | filename [INFO] [stdout] 64 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/sources.rs:74:17 [INFO] [stdout] | [INFO] [stdout] 74 | / warn_user!( [INFO] [stdout] 75 | | "The file `{}` appears to be a `{}` file, but overrides must be specified in `requirements.txt` format.", [INFO] [stdout] 76 | | path.user_display(), [INFO] [stdout] 77 | | filename [INFO] [stdout] 78 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-workspace/src/workspace.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | warn_user!("{err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/pyproject.rs:413:13 [INFO] [stdout] | [INFO] [stdout] 413 | / warn_user_once!( [INFO] [stdout] 414 | | "Missing version constraint (e.g., a lower bound) for `{}`", [INFO] [stdout] 415 | | requirement.name [INFO] [stdout] 416 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/pyproject.rs:499:17 [INFO] [stdout] | [INFO] [stdout] 499 | / warn_user_once!( [INFO] [stdout] 500 | | "Missing version constraint (e.g., a lower bound) for `{}`", [INFO] [stdout] 501 | | requirement.name [INFO] [stdout] 502 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user_once` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/sources.rs:46:17 [INFO] [stdout] | [INFO] [stdout] 46 | / warn_user!( [INFO] [stdout] 47 | | "The file `{}` appears to be a `{}` file, but requirements must be specified in `requirements.txt` format.", [INFO] [stdout] 48 | | path.user_display(), [INFO] [stdout] 49 | | filename [INFO] [stdout] 50 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/sources.rs:60:17 [INFO] [stdout] | [INFO] [stdout] 60 | / warn_user!( [INFO] [stdout] 61 | | "The file `{}` appears to be a `{}` file, but constraints must be specified in `requirements.txt` format.", [INFO] [stdout] 62 | | path.user_display(), [INFO] [stdout] 63 | | filename [INFO] [stdout] 64 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-requirements/src/sources.rs:74:17 [INFO] [stdout] | [INFO] [stdout] 74 | / warn_user!( [INFO] [stdout] 75 | | "The file `{}` appears to be a `{}` file, but overrides must be specified in `requirements.txt` format.", [INFO] [stdout] 76 | | path.user_display(), [INFO] [stdout] 77 | | filename [INFO] [stdout] 78 | | ); [INFO] [stdout] | |_________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-workspace/src/workspace.rs:52:21 [INFO] [stdout] | [INFO] [stdout] 52 | warn_user!("{err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `schemars` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/bench/benches/uv.rs:141:28 [INFO] [stdout] | [INFO] [stdout] 141 | fn build_isolation(&self) -> BuildIsolation { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 141 | fn build_isolation(&self) -> BuildIsolation<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-resolver/tests/resolver.rs:64:24 [INFO] [stdout] | [INFO] [stdout] 64 | fn build_isolation(&self) -> BuildIsolation { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 64 | fn build_isolation(&self) -> BuildIsolation<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-installer v0.0.1 (/opt/rustwide/workdir/crates/uv-installer) [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-installer/src/compile.rs:74:9 [INFO] [stdout] | [INFO] [stdout] 74 | warn_user!("Couldn't determine number of cores, compiling with a single thread: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-installer/src/compile.rs:305:13 [INFO] [stdout] | [INFO] [stdout] 305 | warn_user!("Path contains newline, skipping: {source_file:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-installer/src/compile.rs:74:9 [INFO] [stdout] | [INFO] [stdout] 74 | warn_user!("Couldn't determine number of cores, compiling with a single thread: {err}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-installer/src/compile.rs:305:13 [INFO] [stdout] | [INFO] [stdout] 305 | warn_user!("Path contains newline, skipping: {source_file:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-installer/src/editable.rs:45:26 [INFO] [stdout] | [INFO] [stdout] 45 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 45 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-installer/src/editable.rs:51:26 [INFO] [stdout] | [INFO] [stdout] 51 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 51 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-installer/src/editable.rs:45:26 [INFO] [stdout] | [INFO] [stdout] 45 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 45 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-installer/src/editable.rs:51:26 [INFO] [stdout] | [INFO] [stdout] 51 | fn installed_version(&self) -> InstalledVersion { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 51 | fn installed_version(&self) -> InstalledVersion<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-dispatch v0.0.1 (/opt/rustwide/workdir/crates/uv-dispatch) [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-dispatch/src/lib.rs:116:24 [INFO] [stdout] | [INFO] [stdout] 116 | fn build_isolation(&self) -> BuildIsolation { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 116 | fn build_isolation(&self) -> BuildIsolation<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> crates/uv-dispatch/src/lib.rs:116:24 [INFO] [stdout] | [INFO] [stdout] 116 | fn build_isolation(&self) -> BuildIsolation { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 116 | fn build_isolation(&self) -> BuildIsolation<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking uv-dev v0.0.1 (/opt/rustwide/workdir/crates/uv-dev) [INFO] [stdout] warning: unexpected `cfg` condition name: `macos` [INFO] [stdout] --> crates/uv/tests/pip_sync.rs:3028:12 [INFO] [stdout] | [INFO] [stdout] 3028 | #[cfg_attr(macos, ignore = "The bytecode trace is spuriously different on macOS")] [INFO] [stdout] | ^^^^^ help: found config with similar value: `target_os = "macos"` [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(macos)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(macos)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:54:13 [INFO] [stdout] | [INFO] [stdout] 54 | println!("{schema_string}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | println!("Up-to-date: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:75:21 [INFO] [stdout] | [INFO] [stdout] 75 | println!("Up-to-date: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | println!("Updating: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:82:17 [INFO] [stdout] | [INFO] [stdout] 82 | println!("Updating: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/resolve_cli.rs:144:13 [INFO] [stdout] | [INFO] [stdout] 144 | println!("{}", requirements.iter().map(ToString::to_string).join(" ")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/resolve_cli.rs:148:17 [INFO] [stdout] | [INFO] [stdout] 148 | println!("{}", package); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/wheel_metadata.rs:39:5 [INFO] [stdout] | [INFO] [stdout] 39 | println!("{metadata:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/main.rs:93:13 [INFO] [stdout] | [INFO] [stdout] 93 | println!("Wheel built to {}", target.display()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/main.rs:163:9 [INFO] [stdout] | [INFO] [stdout] 163 | eprintln!("{}", "uv-dev failed".red().bold()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/main.rs:165:13 [INFO] [stdout] | [INFO] [stdout] 165 | eprintln!(" {}: {}", "Caused by".red().bold(), err); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:54:13 [INFO] [stdout] | [INFO] [stdout] 54 | println!("{schema_string}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:59:21 [INFO] [stdout] | [INFO] [stdout] 59 | println!("Up-to-date: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:75:21 [INFO] [stdout] | [INFO] [stdout] 75 | println!("Up-to-date: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:77:21 [INFO] [stdout] | [INFO] [stdout] 77 | println!("Updating: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/generate_json_schema.rs:82:17 [INFO] [stdout] | [INFO] [stdout] 82 | println!("Updating: {filename}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/resolve_cli.rs:144:13 [INFO] [stdout] | [INFO] [stdout] 144 | println!("{}", requirements.iter().map(ToString::to_string).join(" ")); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/resolve_cli.rs:148:17 [INFO] [stdout] | [INFO] [stdout] 148 | println!("{}", package); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/wheel_metadata.rs:39:5 [INFO] [stdout] | [INFO] [stdout] 39 | println!("{metadata:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/main.rs:93:13 [INFO] [stdout] | [INFO] [stdout] 93 | println!("Wheel built to {}", target.display()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/main.rs:163:9 [INFO] [stdout] | [INFO] [stdout] 163 | eprintln!("{}", "uv-dev failed".red().bold()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv-dev/src/main.rs:165:13 [INFO] [stdout] | [INFO] [stdout] 165 | eprintln!(" {}: {}", "Caused by".red().bold(), err); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/cache_dir.rs:7:5 [INFO] [stdout] | [INFO] [stdout] 7 | anstream::println!("{}", cache.root().user_display().cyan()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `anstream::println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_compile.rs:186:13 [INFO] [stdout] | [INFO] [stdout] 186 | / warn_user!( [INFO] [stdout] 187 | | "The requested Python version {} is not available; {} will be used to build dependencies instead.", [INFO] [stdout] 188 | | python_version.version(), [INFO] [stdout] 189 | | interpreter.python_version(), [INFO] [stdout] 190 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_compile.rs:555:13 [INFO] [stdout] | [INFO] [stdout] 555 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_install.rs:443:17 [INFO] [stdout] | [INFO] [stdout] 443 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_install.rs:922:21 [INFO] [stdout] | [INFO] [stdout] 922 | / ... warn_user!( [INFO] [stdout] 923 | | ... "Failed to uninstall package at {} due to missing RECORD file. Installation may result in an incomplete environment.", [INFO] [stdout] 924 | | ... dist_info.path().user_display().cyan(), [INFO] [stdout] 925 | | ... ); [INFO] [stdout] | |_______^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_sync.rs:387:17 [INFO] [stdout] | [INFO] [stdout] 387 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_sync.rs:462:21 [INFO] [stdout] | [INFO] [stdout] 462 | / ... warn_user!( [INFO] [stdout] 463 | | ... "Failed to uninstall package at {} due to missing RECORD file. Installation may result in an incomplete environment.", [INFO] [stdout] 464 | | ... dist_info.path().user_display().cyan(), [INFO] [stdout] 465 | | ... ); [INFO] [stdout] | |_______^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/venv.rs:74:13 [INFO] [stdout] | [INFO] [stdout] 74 | eprint!("{err:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/lock.rs:28:9 [INFO] [stdout] | [INFO] [stdout] 28 | warn_user!("`uv lock` is experimental and may change without warning."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/lock.rs:127:13 [INFO] [stdout] | [INFO] [stdout] 127 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | warn_user!("`uv run` is experimental and may change without warning."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/sync.rs:27:9 [INFO] [stdout] | [INFO] [stdout] 27 | warn_user!("`uv sync` is experimental and may change without warning."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:75:13 [INFO] [stdout] | [INFO] [stdout] 75 | / warn_user!( [INFO] [stdout] 76 | | "pip-compile's `--allow-unsafe` has no effect (uv can safely pin `pip` and other packages)." [INFO] [stdout] 77 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:81:13 [INFO] [stdout] | [INFO] [stdout] 81 | warn_user!("pip-compile's `--no-allow-unsafe` has no effect (uv can safely pin `pip` and other packages)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:91:13 [INFO] [stdout] | [INFO] [stdout] 91 | / warn_user!( [INFO] [stdout] 92 | | "pip-compile's `--no-reuse-hashes` has no effect (uv doesn't reuse hashes)." [INFO] [stdout] 93 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | / warn_user!( [INFO] [stdout] 100 | | "pip-compile's `--resolver=backtracking` has no effect (uv always backtracks)." [INFO] [stdout] 101 | | ); [INFO] [stdout] | |_____________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:136:13 [INFO] [stdout] | [INFO] [stdout] 136 | / warn_user!( [INFO] [stdout] 137 | | "pip-compile's `--no-emit-trusted-host` has no effect (uv never emits trusted hosts)." [INFO] [stdout] 138 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:148:13 [INFO] [stdout] | [INFO] [stdout] 148 | / warn_user!( [INFO] [stdout] 149 | | "pip-compile's `--no-config` has no effect (uv does not use a configuration file)." [INFO] [stdout] 150 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:160:13 [INFO] [stdout] | [INFO] [stdout] 160 | warn_user!("pip-compile's `--no-emit-options` has no effect (uv never emits options)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:276:13 [INFO] [stdout] | [INFO] [stdout] 276 | / warn_user!( [INFO] [stdout] 277 | | "pip-sync's `--no-config` has no effect (uv does not use a configuration file)." [INFO] [stdout] 278 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:327:13 [INFO] [stdout] | [INFO] [stdout] 327 | / warn_user!( [INFO] [stdout] 328 | | "virtualenv's `--clear` has no effect (uv always clears the virtual environment)." [INFO] [stdout] 329 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:333:13 [INFO] [stdout] | [INFO] [stdout] 333 | / warn_user!( [INFO] [stdout] 334 | | "virtualenv's `--no-seed` has no effect (uv omits seed packages by default)." [INFO] [stdout] 335 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:339:13 [INFO] [stdout] | [INFO] [stdout] 339 | warn_user!("virtualenv's `--no-pip` has no effect (uv omits `pip` by default)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:343:13 [INFO] [stdout] | [INFO] [stdout] 343 | / warn_user!( [INFO] [stdout] 344 | | "virtualenv's `--no-setuptools` has no effect (uv omits `setuptools` by default)." [INFO] [stdout] 345 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:349:13 [INFO] [stdout] | [INFO] [stdout] 349 | warn_user!("virtualenv's `--no-wheel` has no effect (uv omits `wheel` by default)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/printer.rs:57:21 [INFO] [stdout] | [INFO] [stdout] 57 | print!("{s}"); [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `print` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `print` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `print` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/printer.rs:79:21 [INFO] [stdout] | [INFO] [stdout] 79 | eprint!("{s}"); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/main.rs:590:13 [INFO] [stdout] | [INFO] [stdout] 590 | eprintln!("{}: {}", "error".red().bold(), causes.next().unwrap()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/main.rs:592:17 [INFO] [stdout] | [INFO] [stdout] 592 | eprintln!(" {}: {}", "Caused by".red().bold(), err); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/cache_dir.rs:7:5 [INFO] [stdout] | [INFO] [stdout] 7 | anstream::println!("{}", cache.root().user_display().cyan()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `anstream::println` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `anstream::println` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `anstream::println` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_compile.rs:186:13 [INFO] [stdout] | [INFO] [stdout] 186 | / warn_user!( [INFO] [stdout] 187 | | "The requested Python version {} is not available; {} will be used to build dependencies instead.", [INFO] [stdout] 188 | | python_version.version(), [INFO] [stdout] 189 | | interpreter.python_version(), [INFO] [stdout] 190 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_compile.rs:555:13 [INFO] [stdout] | [INFO] [stdout] 555 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_install.rs:443:17 [INFO] [stdout] | [INFO] [stdout] 443 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_install.rs:922:21 [INFO] [stdout] | [INFO] [stdout] 922 | / ... warn_user!( [INFO] [stdout] 923 | | ... "Failed to uninstall package at {} due to missing RECORD file. Installation may result in an incomplete environment.", [INFO] [stdout] 924 | | ... dist_info.path().user_display().cyan(), [INFO] [stdout] 925 | | ... ); [INFO] [stdout] | |_______^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_sync.rs:387:17 [INFO] [stdout] | [INFO] [stdout] 387 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/pip_sync.rs:462:21 [INFO] [stdout] | [INFO] [stdout] 462 | / ... warn_user!( [INFO] [stdout] 463 | | ... "Failed to uninstall package at {} due to missing RECORD file. Installation may result in an incomplete environment.", [INFO] [stdout] 464 | | ... dist_info.path().user_display().cyan(), [INFO] [stdout] 465 | | ... ); [INFO] [stdout] | |_______^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/venv.rs:74:13 [INFO] [stdout] | [INFO] [stdout] 74 | eprint!("{err:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/lock.rs:28:9 [INFO] [stdout] | [INFO] [stdout] 28 | warn_user!("`uv lock` is experimental and may change without warning."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/lock.rs:127:13 [INFO] [stdout] | [INFO] [stdout] 127 | eprint!("{report:?}"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | warn_user!("`uv run` is experimental and may change without warning."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/commands/workspace/sync.rs:27:9 [INFO] [stdout] | [INFO] [stdout] 27 | warn_user!("`uv sync` is experimental and may change without warning."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:75:13 [INFO] [stdout] | [INFO] [stdout] 75 | / warn_user!( [INFO] [stdout] 76 | | "pip-compile's `--allow-unsafe` has no effect (uv can safely pin `pip` and other packages)." [INFO] [stdout] 77 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:81:13 [INFO] [stdout] | [INFO] [stdout] 81 | warn_user!("pip-compile's `--no-allow-unsafe` has no effect (uv can safely pin `pip` and other packages)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:91:13 [INFO] [stdout] | [INFO] [stdout] 91 | / warn_user!( [INFO] [stdout] 92 | | "pip-compile's `--no-reuse-hashes` has no effect (uv doesn't reuse hashes)." [INFO] [stdout] 93 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:99:21 [INFO] [stdout] | [INFO] [stdout] 99 | / warn_user!( [INFO] [stdout] 100 | | "pip-compile's `--resolver=backtracking` has no effect (uv always backtracks)." [INFO] [stdout] 101 | | ); [INFO] [stdout] | |_____________________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:136:13 [INFO] [stdout] | [INFO] [stdout] 136 | / warn_user!( [INFO] [stdout] 137 | | "pip-compile's `--no-emit-trusted-host` has no effect (uv never emits trusted hosts)." [INFO] [stdout] 138 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:148:13 [INFO] [stdout] | [INFO] [stdout] 148 | / warn_user!( [INFO] [stdout] 149 | | "pip-compile's `--no-config` has no effect (uv does not use a configuration file)." [INFO] [stdout] 150 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:160:13 [INFO] [stdout] | [INFO] [stdout] 160 | warn_user!("pip-compile's `--no-emit-options` has no effect (uv never emits options)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:276:13 [INFO] [stdout] | [INFO] [stdout] 276 | / warn_user!( [INFO] [stdout] 277 | | "pip-sync's `--no-config` has no effect (uv does not use a configuration file)." [INFO] [stdout] 278 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:327:13 [INFO] [stdout] | [INFO] [stdout] 327 | / warn_user!( [INFO] [stdout] 328 | | "virtualenv's `--clear` has no effect (uv always clears the virtual environment)." [INFO] [stdout] 329 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:333:13 [INFO] [stdout] | [INFO] [stdout] 333 | / warn_user!( [INFO] [stdout] 334 | | "virtualenv's `--no-seed` has no effect (uv omits seed packages by default)." [INFO] [stdout] 335 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:339:13 [INFO] [stdout] | [INFO] [stdout] 339 | warn_user!("virtualenv's `--no-pip` has no effect (uv omits `pip` by default)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:343:13 [INFO] [stdout] | [INFO] [stdout] 343 | / warn_user!( [INFO] [stdout] 344 | | "virtualenv's `--no-setuptools` has no effect (uv omits `setuptools` by default)." [INFO] [stdout] 345 | | ); [INFO] [stdout] | |_____________^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/compat/mod.rs:349:13 [INFO] [stdout] | [INFO] [stdout] 349 | warn_user!("virtualenv's `--no-wheel` has no effect (uv omits `wheel` by default)."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` which comes from the expansion of the macro `warn_user` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/printer.rs:57:21 [INFO] [stdout] | [INFO] [stdout] 57 | print!("{s}"); [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `print` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `print` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `print` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/printer.rs:79:21 [INFO] [stdout] | [INFO] [stdout] 79 | eprint!("{s}"); [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprint` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprint` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/main.rs:590:13 [INFO] [stdout] | [INFO] [stdout] 590 | eprintln!("{}: {}", "error".red().bold(), causes.next().unwrap()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `test` [INFO] [stdout] --> crates/uv/src/main.rs:592:17 [INFO] [stdout] | [INFO] [stdout] 592 | eprintln!(" {}: {}", "Caused by".red().bold(), err); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `axoupdater`, `default`, `git`, `maturin`, `pypi`, `python`, `python-patch`, `self-update`, and `tracing-durations-export` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `eprintln` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `eprintln` may come from an old version of the `anstream` crate, try updating your dependency with `cargo update -p anstream` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `eprintln` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 9m 06s [INFO] running `Command { std: "docker" "inspect" "8cac65bd02f5587ca7c1c18e8e905f9abef3a21a5d396b72078b8b3d99130bb7", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "8cac65bd02f5587ca7c1c18e8e905f9abef3a21a5d396b72078b8b3d99130bb7", kill_on_drop: false }` [INFO] [stdout] 8cac65bd02f5587ca7c1c18e8e905f9abef3a21a5d396b72078b8b3d99130bb7