service add-job overwrites existing actions; daemon exit-0 skips retry_policy #106

Open
opened 2026-05-18 15:33:50 +00:00 by zaelgohary · 1 comment
Member

cmd_add_job builds a fresh ServiceSpec with actions: vec![name], so a second add-job under the same service replaces the start trigger (e.g. hero_aibroker_admin clobbers hero_aibroker_server).

apply_exit_status short-circuits on status.success() for process jobs and marks them Failed without consulting retry_policy, so a daemon that voluntarily exits 0 never retries.

cmd_add_job builds a fresh ServiceSpec with actions: vec![name], so a second add-job under the same service replaces the start trigger (e.g. hero_aibroker_admin clobbers hero_aibroker_server). apply_exit_status short-circuits on status.success() for process jobs and marks them Failed without consulting retry_policy, so a daemon that voluntarily exits 0 never retries.
Author
Member
03e7ed8
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_proc#106
No description provided.