# rustc version rustc 1.98.0-nightly (61d7280f3 2026-06-06)
# docs.rs version docsrs 0.0.0 (39849b9c22c419f6b690c8d2213455bc7426a6b8 2026-06-03 )
# 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" "4d76c6dcbe52e237b27575e12926408508a30b64bbd5c14e7d88ebebe43f9e66" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260606-1.98.0-nightly-61d7280f3\", \"--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 open_creator_protocol v0.4.2 (/opt/rustwide/workdir) [INFO] [stderr] warning: unexpected `cfg` condition value: `custom-heap` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `$crate::custom_heap_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `solana` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `helenos`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `motor`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `qurt`, `redox`, `rtems`, `solaris`, and `solid_asp3` and 14 more [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::custom_heap_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `custom-panic` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::custom_panic_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `solana` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `helenos`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `motor`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `qurt`, `redox`, `rtems`, `solaris`, and `solid_asp3` and 14 more [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::custom_panic_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/policy/init_policy.rs:10:10 [INFO] [stderr] | [INFO] [stderr] 10 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/policy/update_policy.rs:13:10 [INFO] [stderr] | [INFO] [stderr] 13 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/approve.rs:14:10 [INFO] [stderr] | [INFO] [stderr] 14 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/burn.rs:15:10 [INFO] [stderr] | [INFO] [stderr] 15 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/close.rs:14:10 [INFO] [stderr] | [INFO] [stderr] 14 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/init_account.rs:14:10 [INFO] [stderr] | [INFO] [stderr] 14 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/lock.rs:10:10 [INFO] [stderr] | [INFO] [stderr] 10 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/migrate_to_mpl.rs:16:10 [INFO] [stderr] | [INFO] [stderr] 16 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/mint_to.rs:14:10 [INFO] [stderr] | [INFO] [stderr] 14 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/revoke.rs:14:10 [INFO] [stderr] | [INFO] [stderr] 14 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/transfer.rs:14:10 [INFO] [stderr] | [INFO] [stderr] 14 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/unlock.rs:9:10 [INFO] [stderr] | [INFO] [stderr] 9 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/instructions/nft_proxy/wrap.rs:12:10 [INFO] [stderr] | [INFO] [stderr] 12 | #[derive(Accounts)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `program` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `no-log-ix-name` [INFO] [stderr] --> src/lib.rs:14:1 [INFO] [stderr] | [INFO] [stderr] 14 | #[program] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `cpi`, `default`, `no-entrypoint`, `no-idl`, and `test-bpf` [INFO] [stderr] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `program` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `open_creator_protocol` (lib doc) generated 25 warnings (5 duplicates) [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.20s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/open_creator_protocol/index.html [INFO] running `Command { std: "docker" "inspect" "4d76c6dcbe52e237b27575e12926408508a30b64bbd5c14e7d88ebebe43f9e66", kill_on_drop: false }`