farhoodlabs/devcontainer
8
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 39 Wiki Activity

fix: remove stale Happy daemon lock file on startup #17

Merged
cpfarhood merged 2 commits from fix/happy-daemon-stale-lock into main 2026-02-20 15:21:53 +00:00
Conversation 0 Commits 2 Files Changed 2
+6 -1
cpfarhood commented 2026-02-20 15:18:22 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

daemon.state.json.lock is left behind in HAPPY_HOME_DIR when the daemon crashes or the pod is killed/restarted. On next startup happy daemon start sees the lock file and silently exits with Failed to start daemon, leaving no daemon running.

Since the lock lives on the PVC (/home/user/.happy/) it persists across pod restarts, causing every subsequent boot to fail.

The fix is to remove the lock unconditionally before starting — if no daemon is running, the lock is stale by definition.

Test plan

  • Confirm rm ~/.happy/daemon.state.json.lock && happy daemon start works in current pod
  • Deploy updated image, restart pod
  • Confirm daemon starts automatically and happy daemon status shows running
  • Confirm mobile/webapp respond

🤖 Generated with Claude Code

## Summary `daemon.state.json.lock` is left behind in `HAPPY_HOME_DIR` when the daemon crashes or the pod is killed/restarted. On next startup `happy daemon start` sees the lock file and silently exits with `Failed to start daemon`, leaving no daemon running. Since the lock lives on the PVC (`/home/user/.happy/`) it persists across pod restarts, causing every subsequent boot to fail. The fix is to remove the lock unconditionally before starting — if no daemon is running, the lock is stale by definition. ## Test plan - [ ] Confirm `rm ~/.happy/daemon.state.json.lock && happy daemon start` works in current pod - [ ] Deploy updated image, restart pod - [ ] Confirm daemon starts automatically and `happy daemon status` shows running - [ ] Confirm mobile/webapp respond 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
antigravity
architecture
automation
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 examples
good first issue
Good for newcomers
 helm
help wanted
Extra attention is needed
 invalid
This doesn't seem right
 maintainability
monitoring
question
Further information is requested
 refactor
tooling
user-experience
validation
wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
fl_blake (Blake MIddleware) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) flux (Flux CD) admin (Gitea Admin) fl_hugh (Hugh Commit) renovate (Mend Renovate) fl_warren (Warren Bufferpool)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: farhoodlabs/devcontainer#17
Delete Branch "fix/happy-daemon-stale-lock"

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?