Trash follow-ups: restore after a space rename, reserving ".trash" as a folder name, purge audit path #909

Closed
opened 2026-10-15 10:09:44 +00:00 by Cordy · 1 comment
Owner

Follow-ups from the #906 research (comment 9152), decided to be filed separately (Nikola, 2026-10-15). Research first when picked up.

  1. Trash records may still name the old space folder after a space rename (unverified), so a restore could recreate the old folder instead of landing in the renamed space.
  2. Reserving the .trash name for user-created folders (today a user can create a folder named .trash in a normal place; check the impact on hiding and the #897/fix-897b trash filters).
  3. User purges are audited as trash:<id> instead of the original path, which makes the audit hard to read.
Follow-ups from the #906 research (comment 9152), decided to be filed separately (Nikola, 2026-10-15). Research first when picked up. 1. Trash records may still name the old space folder after a space rename (unverified), so a restore could recreate the old folder instead of landing in the renamed space. 2. Reserving the `.trash` name for user-created folders (today a user can create a folder named `.trash` in a normal place; check the impact on hiding and the #897/fix-897b trash filters). 3. User purges are audited as `trash:<id>` instead of the original path, which makes the audit hard to read.
Author
Owner

Closing as superseded:

  • Restore after a space rename: fixed in v0.6.345 (#911). The remaining rename edge cases are in #918.
  • Reserving ".trash": in #926.
  • Purge audit path: in #920.
Closing as superseded: - **Restore after a space rename:** fixed in v0.6.345 (#911). The remaining rename edge cases are in #918. - **Reserving ".trash":** in #926. - **Purge audit path:** in #920.
Cordy closed this issue 2026-10-15 21:48:42 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#909
No description provided.