Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-b4"
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?
Batch 4 of the backlog run. Decisions on #915, #920, #926 and #971 are recorded on each issue.
What changes
Deleted files and audit
by, the audituser(plus a newownerfield), lock checks, leak tracing and device-paused records. Keys, paths and quota are unchanged. The owner's Deleted files row shows the chip "{folder} · {name}".manual-purge(original path, entry id), and admin manual-purge uses the same format.write, and trash paths never leak into it.API
destination-existsunless the request sendsoverwrite: true. Copy's 409 gets the same code..trashis trash only at/.trashand/spaces/<x>/.trash; anywhere else it is an ordinary folder. Creating.trashat a space root, or at the root in flat mode, is refused withname-reserved: 409 on REST, TUS and the drop link, 403 on WebDAV and OCM.log.level/CAIRN_LOG_LEVELsetting, which never affects the audit log. The OIDC confirmation line is now INFO, and a missingauth_timegives an hourly WARN.Claims.Reauthedis removed.Activity (#916, #971, privacy)
activity-v2.json.Storage (#963 / #976)
Process
-raceruns on the batch-4 tests;go vet, gofmt and the web checks pass; no U+2014..superpowers/sdd/2026-10-19-batch4/.Follow-ups filed: #971 (part), #973, #974, #975, #977, #978, #979, #980, #981, #982, #983, and notes on #742.
Release gate: a live screenshot OK for the #915 chip.
The owner's row gets the chip space rows already use, "{folder} · {name}" (the item's parent folder as the owner sees it, the deleter's display name), with "Deleted by {name}" on hover in EN, DE, FR and IT. The viewer's own deletions show no chip. Administration > Deleted files already shows by for personal rows and is unchanged.Status (2026-10-20): v0.6.351 is merged and tagged, the image is built, and both dogfoods are bumped (homelab-config 3336a8d). Both started cleanly on v0.6.351.
Activity conversion at first start (#971):
S3 folder-name probe (files-bao): no WARN, so Garage answers HEAD of a folder name with 404.
Still open (Nikola signs in on both instances):