TEMPLATE_HERO_REPOS contains repos that arent on Forge / dont have a Cargo.toml — clean up #294
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_skills#294
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
crates/lab/src/pod/pod_template.rs::TEMPLATE_HERO_REPOSlists every hero_* repo the operator wants in/home/template/hero/. Onlab flow template build --releasetoday, three entries fail with non-recoverable errors that point at the catalog being stale, not at any real build issue:Suggested action
For each entry: either fix the underlying repo or remove from the catalog.
Cargo.toml. Either the repo is python-only (then it shouldnt be in the rust-build catalog) or the checkout is broken — investigate.hero_admin_libssh-git fetch fromhero_website_framework. Eitherhero_bundleshould use the public https URL via the cargo[url]rewrite, or it shouldnt depend onhero_website_frameworkfor the bundle target.Cleaning the catalog reduces noise in template-build failure reports and lets operators focus on real regressions.
Confirmed from this morning's
lab flow template build --release(cf500cf6lab + 87bcc2a hero_codescalers) — the 3 Cat-A entries that should be commented out ofTEMPLATE_HERO_REPOS: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:
1993bfb5