shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Queue daemon: implement timeout handling for long-running tasks #166

New Issue
Closed
opened 2026-04-06 02:07:43 +02:00 by shoko · 1 comment
shoko commented 2026-04-06 02:07:43 +02:00
Owner
Copy Link

Problem

The queue daemon spawns tasks via cmd_start/cmd_continue but never kills them if they run too long. Tasks can run indefinitely if:

  • The opencode session hangs
  • Network issues cause stalls
  • The agent gets stuck in a loop

Current Behavior

  • No timeout is enforced
  • Tasks stay in 'notified' state forever if the process never terminates
  • No mechanism to kill stuck tasks and mark them as error

Expected Fix

  1. Add TASK_TIMEOUT_HOURS configuration (already defined but not used)
  2. Track task start time when setting state to 'notified'
  3. In check_task_completion(), check if task exceeded timeout
  4. If timeout exceeded, kill the process and set state to 'error'

Severity

Low - enhancement, tasks eventually complete or are manually cleaned up

## Problem The queue daemon spawns tasks via cmd_start/cmd_continue but never kills them if they run too long. Tasks can run indefinitely if: - The opencode session hangs - Network issues cause stalls - The agent gets stuck in a loop ## Current Behavior - No timeout is enforced - Tasks stay in 'notified' state forever if the process never terminates - No mechanism to kill stuck tasks and mark them as error ## Expected Fix 1. Add TASK_TIMEOUT_HOURS configuration (already defined but not used) 2. Track task start time when setting state to 'notified' 3. In check_task_completion(), check if task exceeded timeout 4. If timeout exceeded, kill the process and set state to 'error' ## Severity Low - enhancement, tasks eventually complete or are manually cleaned up
shoko added the ready label 2026-04-07 08:55:25 +02:00
shoko commented 2026-04-08 04:39:55 +02:00
Author
Owner
Copy Link

@han Updated! Changed echo to log_warn/log_error for the timeout messages. Good catch on using kugetsu-log for unified formatting.

@han Updated! Changed echo to log_warn/log_error for the timeout messages. Good catch on using kugetsu-log for unified formatting.
shoko closed this issue 2026-04-08 04:51:54 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label ready
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#166
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?