nixbot

python3.14-firecrawl-py-2.8.0:
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
Executing pythonImportsCheckPhase
Check whether the following modules can be imported: firecrawl
Executing pythonMetadataCheckPhase
The 'firecrawl-py' derivation has version '2.8.0' but .dist-info/METADATA specifies version '4.14.0'.
This usually means that the wrong version is hardcoded in pyproject.toml or setup.{py,cfg}.
Use the pyprojectVersionPatchHook or patch the version manually so that the project metadata matches the derivation's version.

goose-cli-1.44.0:
   Compiling goose-cli v1.44.0 (/build/source/crates/goose-cli)
thread 'main' (28153) panicked at cargo-auditable/src/rustc_wrapper.rs:35:10:
rustc was terminated by a deadly signal
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: could not compile `goose` (lib)
Caused by:
  process didn't exit successfully: `/nix/store/95asw04hma2z3ryn3gh4nvrsin5nrw3v-cargo-auditable-0.7.5/bin/cargo-auditable rustc --crate-name goose --edition=2021 crates/goose/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no '--allow=clippy::uninlined_format_args' '--warn=clippy::string_slice' --cfg 'feature="aws-providers"' --cfg 'feature="code-mode"' --cfg 'feature="local-inference"' --cfg 'feature="nostr"' --cfg 'feature="otel"' --cfg 'feature="rustls-tls"' --cfg 'feature="system-keyring"' --cfg 'feature="telemetry"' -…
warning: build failed, waiting for other jobs to finish...

python3.14-firecrawl-py-2.8.0:
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
Executing pythonImportsCheckPhase
Check whether the following modules can be imported: firecrawl
Executing pythonMetadataCheckPhase
The 'firecrawl-py' derivation has version '2.8.0' but .dist-info/METADATA specifies version '4.14.0'.
This usually means that the wrong version is hardcoded in pyproject.toml or setup.{py,cfg}.
Use the pyprojectVersionPatchHook or patch the version manually so that the project metadata matches the derivation's version.

lean-ctx-3.9.12:
   Compiling tikv-jemallocator v0.7.0
   Compiling tikv-jemalloc-ctl v0.7.0
thread 'main' (14503) panicked at cargo-auditable/src/rustc_wrapper.rs:35:10:
rustc was terminated by a deadly signal
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: could not compile `lean-ctx` (bin "lean-ctx")
Caused by:
  process didn't exit successfully: `/nix/store/95asw04hma2z3ryn3gh4nvrsin5nrw3v-cargo-auditable-0.7.5/bin/cargo-auditable rustc --crate-name lean_ctx --edition=2024 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin --emit=dep-info,link -C opt-level=z -C lto -C codegen-units=1 '--warn=clippy::pedantic' '--allow=clippy::used_underscore_binding' '--allow=clippy::unreadable_literal' --warn=unreachable_pub --warn=unexpected_cfgs '--allow=clippy::trivially_copy_pass_by_ref' '--allow=clippy::too_many_lines' '--allow=clippy::struct_excessive_bools' '--allow=clippy::similar_names' '--allow=cli…

openclaw-2026.7.1:
[tsdown-build] still running pid=1068; no output for 30s
[tsdown-build] still running pid=1068; no output for 30s
[tsdown-build] still running pid=1068; no output for 30s
undefined
 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command was killed with SIGKILL (Forced termination): tsdown --config-loader unrun --logLevel warn --no-clean
[build-all] tsdown failed after 1140.3s
[build-all] phase timings: total 1145.7s; slowest tsdown (failed) 1140.3s; plugins:assets:build 5.44s
 ELIFECYCLE  Command failed with exit code 1.

python3.14-firecrawl-py-2.8.0:
Executing pythonRemoveTestsDir
Finished executing pythonRemoveTestsDir
Executing pythonImportsCheckPhase
Check whether the following modules can be imported: firecrawl
Executing pythonMetadataCheckPhase
The 'firecrawl-py' derivation has version '2.8.0' but .dist-info/METADATA specifies version '4.14.0'.
This usually means that the wrong version is hardcoded in pyproject.toml or setup.{py,cfg}.
Use the pyprojectVersionPatchHook or patch the version manually so that the project metadata matches the derivation's version.