[service_complete] should soft-fail per service so one failure doesn't take down the rest #234
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#234
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?
Surfaced during session 74.
Symptom
service_complete --downloadhard-errors at the first failing service. Operators don't see the full picture of what works and what doesn't until they hand-patch the loop.Current behavior
packages.nuservice_completedoes:The
error makeshort-circuits the loop. One bad release / one missing dep = no information about anything downstream.Proposed fix
Replace the
error makewith afailedaccumulator. Continue the loop. Print a summary at the end:This is what session 74's hand-patch did.
Severity
Medium — usability + investigation efficiency. Doesn't block the happy path, but every from-nothing test surfaces multiple issues and you only see one at a time.
Pairs with #(this issue's # for cargo-only-skip) and the upstream-debt cluster from session 74.
Filed as part of home#227 follow-ups.
mik-tf referenced this issue from lhumina_code/hero_demo2026-05-07 18:31:17 +00:00