A root 0031 could not normalise still cannot be edited #249
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: yolo/arr#249
Reference in New Issue
Block a user
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?
Migration 0031 deliberately skips normalising a root whose stripped path another
row already holds, so the migration cannot fail to apply. Its comment calls the
leftover "a settings mistake for the operator to resolve by hand".
There is no hand-resolution path. For such a row,
roots.rs:207takes theno-relocation branch, because the normalised payload equals the normalised
current value, so
path_is_freeis skipped — and then theUPDATEatroots.rs:214writes the normalised path straight into theUNIQUEindex andreturns
root_conflict, a 409, even for a policy-only edit. The operator's onlyway out is deleting the root.
Very low severity:
rootsalso carriesUNIQUE (kind, audience), so the tableholds at most four rows, and getting into this state needs two roots that differ
only by a trailing separator.
Scope: either detect the collision and return an error that says what is wrong
and which other root holds the path, or let the operator edit the row's other
fields without touching its path.