kindred/create
1
1
Fork 0
Code Issues 53 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

feat(silo): implement file locking to prevent concurrent edits #61

New Issue
Closed
opened 2026-02-08 23:26:35 +00:00 by forbes · 0 comments
forbes commented 2026-02-08 23:26:35 +00:00
Owner
Copy Link

Pessimistic locks on Silo_Open to prevent concurrent edits of the same document.

Needed:

  • Server-side lock table and lock/unlock API endpoints
  • Client-side lock acquisition on open, release on close/save
  • Lock status display in the UI (show who has the file locked)
  • Lock timeout/expiry for stale locks

Source: KNOWN_ISSUES.md — Incomplete features

Pessimistic locks on `Silo_Open` to prevent concurrent edits of the same document. **Needed:** - Server-side lock table and lock/unlock API endpoints - Client-side lock acquisition on open, release on close/save - Lock status display in the UI (show who has the file locked) - Lock timeout/expiry for stale locks **Source:** KNOWN_ISSUES.md — Incomplete features
forbes added the enhancement label 2026-02-08 23:26:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
UX
branding
bug
ci/cd
CI/CD workflows and deployment
 defaults
documentation
Developer documentation
 enhancement
high-priority
low-priority
theme
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
forbes
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kindred/create#61
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?