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

Queue daemon crashes with unbound GITEA_TOKEN variable #160

New Issue
Closed
opened 2026-04-06 01:00:58 +02:00 by shoko · 0 comments
shoko commented 2026-04-06 01:00:58 +02:00
Owner
Copy Link

Bug

When the queue daemon runs cmd_continue, it fails with GITEA_TOKEN: unbound variable because the subshell does not inherit the variable from the parent shell.

Root Cause

cmd_continue uses:

nohup sh -c "GITEA_TOKEN='${GITEA_TOKEN:-}' opencode run '$message' --continue --session '$pm_session' >> '$log_file' 2>&1" > /dev/null 2>&1 &

The subshell cannot expand ${GITEA_TOKEN:-} because the variable is not set in the daemon's environment.

Fix

Source ~/.kugetsu/env/pm-agent.env at daemon startup so GITEA_TOKEN is available. The daemon currently only sources default.env which doesn't contain the token.

## Bug When the queue daemon runs `cmd_continue`, it fails with `GITEA_TOKEN: unbound variable` because the subshell does not inherit the variable from the parent shell. ## Root Cause `cmd_continue` uses: nohup sh -c "GITEA_TOKEN='${GITEA_TOKEN:-}' opencode run '$message' --continue --session '$pm_session' >> '$log_file' 2>&1" > /dev/null 2>&1 & The subshell cannot expand `${GITEA_TOKEN:-}` because the variable is not set in the daemon's environment. ## Fix Source `~/.kugetsu/env/pm-agent.env` at daemon startup so `GITEA_TOKEN` is available. The daemon currently only sources `default.env` which doesn't contain the token.
shoko closed this issue 2026-04-06 01:42:05 +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
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#160
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?