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

feat(kugetsu): add lock mechanism for worktree coordination #96

Merged
shoko merged 1 commits from feat/issue-71-lock-mechanism-v2 into main 2026-04-02 04:52:45 +02:00
Conversation 0 Commits 1 Files Changed 1 +94
shoko commented 2026-04-02 04:20:38 +02:00
Owner
Copy Link

Summary

Fix for #71 - Lock mechanism for worktree coordination.

Changes

Add lock mechanism to prevent concurrent access to worktrees:

  • Add LOCKS_DIR constant (~/.kugetsu/locks)
  • Add acquire_lock() - acquires lock file with PID, session_id, timestamp
  • Add release_lock() - releases lock if held by current process
  • Add release_all_locks() - releases all locks for a session
  • Add check_lock() - check if issue is locked
  • Modify cmd_start to acquire lock before creating worktree
  • Modify cmd_destroy to release lock when destroying session
  • Add trap for cleanup on EXIT/INT/TERM

Lock files named after issue ref. Stale lock detection: if PID no longer exists, lock is considered stale.

Fixes #71

## Summary Fix for #71 - Lock mechanism for worktree coordination. ## Changes Add lock mechanism to prevent concurrent access to worktrees: - Add LOCKS_DIR constant (~/.kugetsu/locks) - Add acquire_lock() - acquires lock file with PID, session_id, timestamp - Add release_lock() - releases lock if held by current process - Add release_all_locks() - releases all locks for a session - Add check_lock() - check if issue is locked - Modify cmd_start to acquire lock before creating worktree - Modify cmd_destroy to release lock when destroying session - Add trap for cleanup on EXIT/INT/TERM Lock files named after issue ref. Stale lock detection: if PID no longer exists, lock is considered stale. Fixes #71
shoko added 1 commit 2026-04-02 04:20:38 +02:00
feat(kugetsu): add lock mechanism for worktree coordination 59061a9c03 
Add lock mechanism to prevent concurrent access to worktrees:
- Add LOCKS_DIR constant (~/.kugetsu/locks)
- Add acquire_lock() - acquires lock file with PID, session_id, timestamp
- Add release_lock() - releases lock if held by current process
- Add release_all_locks() - releases all locks for a session
- Add check_lock() - check if issue is locked
- Modify cmd_start to acquire lock before creating worktree
- Modify cmd_destroy to release lock when destroying session
- Add trap for cleanup on EXIT/INT/TERM

Lock files named after issue ref. Stale lock detection: if PID
no longer exists, lock is considered stale.

Fixes #71
shoko force-pushed feat/issue-71-lock-mechanism-v2 from 59061a9c03 to 990bc46477 2026-04-02 04:52:26 +02:00 Compare
shoko merged commit 8a72509452 into main 2026-04-02 04:52:45 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
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#96
Delete Branch "feat/issue-71-lock-mechanism-v2"

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?