TEMPLATE_HERO_REPOS contains repos that arent on Forge / dont have a Cargo.toml — clean up #294

Closed
opened 2026-05-25 06:03:56 +00:00 by zaelgohary · 2 comments
Member

crates/lab/src/pod/pod_template.rs::TEMPLATE_HERO_REPOS lists every hero_* repo the operator wants in /home/template/hero/. On lab flow template build --release today, three entries fail with non-recoverable errors that point at the catalog being stale, not at any real build issue:

=== [16/42] lab build hero_claude ===
→ hero_claude not found locally, searching Forge…
lab build: repo not found: hero_claude
  ✗ hero_claude failed: exit 1

=== [24/42] lab build hero_hermes ===
→ building in /home/template/hero/code/hero_hermes
lab build: no Cargo.toml found above /home/template/hero/code/hero_hermes
  ✗ hero_hermes failed: exit 1

=== [15/42] lab build hero_bundle ===
warning: spurious network error (3 tries remaining): process didnt exit successfully: git fetch --tags --force --update-head-ok ssh://git@forge.ourworld.tf/lhumina_code/hero_website_framework.git
error: failed to load source for dependency hero_admin_lib
lab build: no Cargo.toml found under /home/template/hero/code/hero_bundle
  ✗ hero_bundle failed: exit 1

Suggested action

For each entry: either fix the underlying repo or remove from the catalog.

  • hero_claude — does this repo exist anywhere? If yes, fix the Forge URL; if no, drop from the list.
  • hero_hermes — checkout missing Cargo.toml. Either the repo is python-only (then it shouldnt be in the rust-build catalog) or the checkout is broken — investigate.
  • hero_bundle — fails on hero_admin_lib ssh-git fetch from hero_website_framework. Either hero_bundle should use the public https URL via the cargo [url] rewrite, or it shouldnt depend on hero_website_framework for the bundle target.

Cleaning the catalog reduces noise in template-build failure reports and lets operators focus on real regressions.

`crates/lab/src/pod/pod_template.rs::TEMPLATE_HERO_REPOS` lists every hero_* repo the operator wants in `/home/template/hero/`. On `lab flow template build --release` today, three entries fail with non-recoverable errors that point at the catalog being stale, not at any real build issue: ``` === [16/42] lab build hero_claude === → hero_claude not found locally, searching Forge… lab build: repo not found: hero_claude ✗ hero_claude failed: exit 1 === [24/42] lab build hero_hermes === → building in /home/template/hero/code/hero_hermes lab build: no Cargo.toml found above /home/template/hero/code/hero_hermes ✗ hero_hermes failed: exit 1 === [15/42] lab build hero_bundle === warning: spurious network error (3 tries remaining): process didnt exit successfully: git fetch --tags --force --update-head-ok ssh://git@forge.ourworld.tf/lhumina_code/hero_website_framework.git error: failed to load source for dependency hero_admin_lib lab build: no Cargo.toml found under /home/template/hero/code/hero_bundle ✗ hero_bundle failed: exit 1 ``` ## Suggested action For each entry: either fix the underlying repo or remove from the catalog. - **hero_claude** — does this repo exist anywhere? If yes, fix the Forge URL; if no, drop from the list. - **hero_hermes** — checkout missing `Cargo.toml`. Either the repo is python-only (then it shouldnt be in the rust-build catalog) or the checkout is broken — investigate. - **hero_bundle** — fails on `hero_admin_lib` ssh-git fetch from `hero_website_framework`. Either `hero_bundle` should use the public https URL via the cargo `[url]` rewrite, or it shouldnt depend on `hero_website_framework` for the bundle target. Cleaning the catalog reduces noise in template-build failure reports and lets operators focus on real regressions.
Author
Member

Confirmed from this morning's lab flow template build --release (cf500cf6 lab + 87bcc2a hero_codescalers) — the 3 Cat-A entries that should be commented out of TEMPLATE_HERO_REPOS:

// hero_claude        — repo not found on forge.ourworld.tf/lhumina_code
// hero_hermes        — checkout missing Cargo.toml (likely python-only)
// hero_bundle        — depends on hero_admin_lib via ssh://git@... fetch, fails network

Follow-up patch on PR #295 will comment these three back out, since they fail at the catalog level and only generate noise without producing binaries.

The other 6 broken builds from the same run (hero_foundry, hero_foundry_ui, hero_gpu, hero_rpc/walkthrough, hero_cloud_bootstrapper, hero_code, hero_runner_py) stay uncommented — those are tracked separately:

  • hero_foundry/hero_foundry_ui/hero_gpu/hero_walkthrough → #293 (lab --info check kills working binaries)
  • hero_cloud_bootstrapper → hero_cloud_bootstrapper#1
  • hero_code → hero_code#16
  • hero_runner_py → hero_runner_py#1
Confirmed from this morning's `lab flow template build --release` (cf500cf6 lab + 87bcc2a hero_codescalers) — the 3 Cat-A entries that should be commented out of `TEMPLATE_HERO_REPOS`: ``` // hero_claude — repo not found on forge.ourworld.tf/lhumina_code // hero_hermes — checkout missing Cargo.toml (likely python-only) // hero_bundle — depends on hero_admin_lib via ssh://git@... fetch, fails network ``` Follow-up patch on PR #295 will comment these three back out, since they fail at the catalog level and only generate noise without producing binaries. The other 6 broken builds from the same run (hero_foundry, hero_foundry_ui, hero_gpu, hero_rpc/walkthrough, hero_cloud_bootstrapper, hero_code, hero_runner_py) stay uncommented — those are tracked separately: - hero_foundry/hero_foundry_ui/hero_gpu/hero_walkthrough → #293 (lab --info check kills working binaries) - hero_cloud_bootstrapper → hero_cloud_bootstrapper#1 - hero_code → hero_code#16 - hero_runner_py → hero_runner_py#1
Author
Member
1993bfb5
Sign in to join this conversation.
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_skills#294
No description provided.