Source-build fail: hero_os build-script panic exit 101 in desktop OSchema generator #130

New issue

Open

opened 2026-05-08 21:22:12 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-08 21:22:12 +00:00

Owner

Source-build failure surfaced by session 80 Phase 0 sweep:

error: failed to run custom build command for `hero_os v0.5.0 (crates/hero_os)`
Caused by:
  process didn't exit successfully: `target/release/build/hero_os-126d8bb1fb117a94/build-script-build` (exit status: 101)
  --- stdout
  ...
  Generator: generating src/desktop/
    Writing: .../desktop/types_generated.rs
    Writing: .../desktop/types_wasm_generated.rs
    Writing: .../desktop/openrpc.json
    Writing: .../desktop/mod.rs
  Generator: generating server_crate/src/desktop/
    Writing: .../hero_os_server/src/desktop/osis_server_generated.rs
    Writing: .../hero_os_server/src/desktop/rpc_generated.rs
  Generator: generating sdk/js/
    Writing: .../sdk/js/types_generated.js
  Generator: generating src/desktop/tests.rs
    Writing: .../hero_os_server/src/desktop/tests.rs

The build-script writes all expected files successfully, then exits with status 101 (Rust panic) with no further visible stderr in the captured tail. Likely an assert! or unwrap() in the OSchema generator after file writes. Per D-03 the fix lives at the generator layer, not in any autogen output.

Status: s80 sweep ran on hero_os 18 commits behind origin/development (now ff-pulled). Some of those commits ("format and reorder imports in desktop modules", "rust-version 1.95.0", "pin hero_ git deps to version 0.6.0") may resolve this on retry. Session 81 hero_builder sweep on synced state will re-test.

Reproduce: cd lhumina_code/hero_os && cargo build --workspace --release. Read full stderr from build_logs/80/hero_os.log if/when needed (workspace tracker only).

Filed at session 80 close.

**Source-build failure** surfaced by session 80 Phase 0 sweep: ``` error: failed to run custom build command for `hero_os v0.5.0 (crates/hero_os)` Caused by: process didn't exit successfully: `target/release/build/hero_os-126d8bb1fb117a94/build-script-build` (exit status: 101) --- stdout ... Generator: generating src/desktop/ Writing: .../desktop/types_generated.rs Writing: .../desktop/types_wasm_generated.rs Writing: .../desktop/openrpc.json Writing: .../desktop/mod.rs Generator: generating server_crate/src/desktop/ Writing: .../hero_os_server/src/desktop/osis_server_generated.rs Writing: .../hero_os_server/src/desktop/rpc_generated.rs Generator: generating sdk/js/ Writing: .../sdk/js/types_generated.js Generator: generating src/desktop/tests.rs Writing: .../hero_os_server/src/desktop/tests.rs ``` The build-script writes all expected files successfully, then exits with status 101 (Rust panic) with no further visible stderr in the captured tail. Likely an `assert!` or `unwrap()` in the OSchema generator after file writes. Per [D-03](https://forge.ourworld.tf/lhumina_code/home/issues/230) the fix lives at the generator layer, not in any autogen output. **Status:** s80 sweep ran on hero_os 18 commits behind `origin/development` (now ff-pulled). Some of those commits ("format and reorder imports in desktop modules", "rust-version 1.95.0", "pin hero_ git deps to version 0.6.0") may resolve this on retry. Session 81 hero_builder sweep on synced state will re-test. **Reproduce:** `cd lhumina_code/hero_os && cargo build --workspace --release`. Read full stderr from `build_logs/80/hero_os.log` if/when needed (workspace tracker only). Filed at session 80 close.