Build failed. If you want to re-trigger a documentation build, you can do it here. You can find more information on docs.rs builds documentation on the builds page.
# error kind ExecutionFailed
# pre-build errors command failed: exit status: 101
# rustc version rustc 1.98.0-nightly (bd08c9e71 2026-06-25)
# docs.rs version docsrs 0.0.0 (886bc7a22b1adc4b387ce1343447fe3af98d9ce5 2026-06-14 )
# build log [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-w" "/opt/rustwide/workdir" "--user" "1001:1001" "a75998be80debd218a132cec9e503fd9358bec2217478d36fd95197579861196" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260625-1.98.0-nightly-bd08c9e71\", \"--static-root-path\", \"/-/rustdoc.static/\", \"--cap-lints\", \"warn\", \"--extern-html-root-takes-precedence\"]" "--offline" "-Zunstable-options" "--config=doc.extern-map.registries.crates-io=\"https://docs.rs/{pkg_name}/{version}/x86_64-unknown-linux-gnu\"" "-Zrustdoc-scrape-examples" "-j6" "--target" "x86_64-unknown-linux-gnu", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting libutils v8.34.20 (/opt/rustwide/workdir) [INFO] [stderr] error: expected a trait, found type [INFO] [stderr] --> array/mod.rs:115:28 [INFO] [stderr] | [INFO] [stderr] 115 | impl<Type, const N: usize> const Default for Array<Type, N> { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error: expected a trait, found type [INFO] [stderr] --> issue/conversions.rs:14:6 [INFO] [stderr] | [INFO] [stderr] 14 | impl const Into<Issue> for &'static str { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error: expected a trait, found type [INFO] [stderr] --> log/mod.rs:39:12 [INFO] [stderr] | [INFO] [stderr] 39 | impl<Type> const Default for Log<Type> { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error: expected a trait, found type [INFO] [stderr] --> problem/severity.rs:10:8 [INFO] [stderr] | [INFO] [stderr] 10 | } impl const Into<&'static str> for &Severity { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error: expected a trait, found type [INFO] [stderr] --> report/mod.rs:43:6 [INFO] [stderr] | [INFO] [stderr] 43 | impl const Default for Report<"Main", 1> { [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error[E0433]: failed to resolve: could not resolve path `Log::new` [INFO] [stderr] --> terminal/layout.rs:19:41 [INFO] [stderr] | [INFO] [stderr] 19 | pub problems: Log<Problem<Issue>> = Log::new() [INFO] [stderr] | ^^^^^^^^ could not resolve path `Log::new` [INFO] [stderr] | [INFO] [stderr] = note: this error was originally ignored because you are running `rustdoc` [INFO] [stderr] = note: try running again with `rustc` or `cargo check` and you may get a more detailed error [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0433`. [INFO] [stderr] error: could not document `libutils` [INFO] running `Command { std: "docker" "inspect" "a75998be80debd218a132cec9e503fd9358bec2217478d36fd95197579861196", kill_on_drop: false }`