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 #279

New Issue
Open
opened 2026-02-19 06:48:25 +00:00 by forbes · 0 comments
forbes commented 2026-02-19 06:48:25 +00:00
Owner
Copy Link

Summary

No file locking mechanism exists. Concurrent edits to the same Silo-tracked document can cause data loss or silent overwrites.

Required

  • Server-side lock table (acquire/release/heartbeat)
  • Lock acquisition on Silo_Open or document activation
  • Lock release on document close
  • Client-side lock status display (who holds the lock)
  • Stale lock detection and forced unlock for admin

References

  • docs/KNOWN_ISSUES.md — incomplete feature: File locking
## Summary No file locking mechanism exists. Concurrent edits to the same Silo-tracked document can cause data loss or silent overwrites. ## Required - Server-side lock table (acquire/release/heartbeat) - Lock acquisition on Silo_Open or document activation - Lock release on document close - Client-side lock status display (who holds the lock) - Stale lock detection and forced unlock for admin ## References - docs/KNOWN_ISSUES.md — incomplete feature: File locking
forbes added the enhancement label 2026-02-19 06:48:25 +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#279
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?