v0.6.391: show the locks an administrator's action carries or ends (#1073) #1081
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lk1073"
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?
Closes #1073.
?locks=1on the estate and space-state answers), never cached.locksCarried/locksBroken/locksReleasedin the answers, status lines and audit notes (0 included when a lock store is wired). Holders get one grouped bell per action with a padlock and no link. A space delete sends the "deleted" bells only after its tombstone is written.tokenorsession.DELETE /api/v1/admin/locks?path=<stored path>, which does a record-level drop. Before, Break answered 404 for locks in other people's homes.Reviewed per wave (W1-W3) plus a final review with adversarial probes; all findings fixed or in the backlog.
S1: PruneBeforeMove keeps the locks the person acting passes (owner transfer only); PruneUnder and PruneHolderUnder release them, so a member administrator removing themselves or an administrator lowering a grant made to themselves loses the locks they can no longer write. N1: nLockGoneN formats {n} with fmtCount. N2: adminLockBreak looks up the path as sent before its NFC form. N3: adminLockBreak and lockRemove remove the record read (Store.UnlockRecord), so a lock re-taken in between stays (404). Docs: ARCHITECTURE, CHANGELOG v0.6.391, admin-policy.