hero_runner_py_server: 3 compile errors in proc_log.rs block template builds #1

New issue

Open

opened 2026-05-25 06:05:33 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-05-25 06:05:33 +00:00

Member

Symptom

lab build on hero_runner_py (development) fails with 3 errors in crates/hero_runner_py_server/src/proc_log.rs:

=== [35/42] lab build hero_runner_py ===
FAILED: hero_runner_py_server:release:x86_64-unknown-linux-gnu
   Compiling hero_runner_py_server v0.1.0
  --> crates/hero_runner_py_server/src/proc_log.rs:28:46
  --> crates/hero_runner_py_server/src/proc_log.rs:21:56
  --> crates/hero_runner_py_server/src/proc_log.rs:66:41
error: could not compile `hero_runner_py_server` (lib) due to 3 previous errors
FAILED: hero_runner_py_admin:release:x86_64-unknown-linux-gnu
error: could not compile `hero_runner_py_server` (lib) due to 3 previous errors
  ✗ hero_runner_py failed: exit 1

Lab truncated the actual error messages. Full diagnostics need to be captured by running cargo locally.

Why it matters

hero_runner_py is in lab::pod::pod_template::TEMPLATE_HERO_REPOS. With it broken, neither hero_runner_py_server nor hero_runner_py_admin lands in /home/template/hero/bin/, so codescalers rollouts ship without python-runner support.

File line numbers (21, 28, 66) suggest a small surface area in proc_log.rs — likely an API change in hero_proc or similar logging crate.

Repro

ssh herodev
sudo -u template -i
cd /home/template/hero/code/hero_runner_py
source /home/template/hero/cfg/init.sh
cargo build --release -p hero_runner_py_server

Should reveal the 3 errors and whichever upstream crate moved.

## Symptom `lab build` on `hero_runner_py` (development) fails with 3 errors in `crates/hero_runner_py_server/src/proc_log.rs`: ``` === [35/42] lab build hero_runner_py === FAILED: hero_runner_py_server:release:x86_64-unknown-linux-gnu Compiling hero_runner_py_server v0.1.0 --> crates/hero_runner_py_server/src/proc_log.rs:28:46 --> crates/hero_runner_py_server/src/proc_log.rs:21:56 --> crates/hero_runner_py_server/src/proc_log.rs:66:41 error: could not compile `hero_runner_py_server` (lib) due to 3 previous errors FAILED: hero_runner_py_admin:release:x86_64-unknown-linux-gnu error: could not compile `hero_runner_py_server` (lib) due to 3 previous errors ✗ hero_runner_py failed: exit 1 ``` Lab truncated the actual error messages. Full diagnostics need to be captured by running cargo locally. ## Why it matters `hero_runner_py` is in `lab::pod::pod_template::TEMPLATE_HERO_REPOS`. With it broken, neither `hero_runner_py_server` nor `hero_runner_py_admin` lands in `/home/template/hero/bin/`, so codescalers rollouts ship without python-runner support. File line numbers (21, 28, 66) suggest a small surface area in `proc_log.rs` — likely an API change in `hero_proc` or similar logging crate. ## Repro ``` ssh herodev sudo -u template -i cd /home/template/hero/code/hero_runner_py source /home/template/hero/cfg/init.sh cargo build --release -p hero_runner_py_server ``` Should reveal the 3 errors and whichever upstream crate moved.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

lhumina_code/hero_runner_py#1

No description provided.

Rows
Columns