fix(sidebar): let a ghost folder be cleared from the UI (#1145)

Deleting a folder a file manager had already moved away answered "Folder no longer
exists" and stopped there: `remove_known_folder()` only ran after `shutil.rmtree()`
succeeded, so the records keeping the node in the tree could never be dropped, and
the modal's missing state hid its confirm button. The sidebar was a dead end for
exactly the case the folder list cannot self-heal.

* `ModelMoveService.forget_folder()` drops a folder's records (the recorded entry
  plus the cached models under it) and refuses with `code: "exists"` while any root
  still holds the directory, because then the caller wants a delete.
* `delete_folder()` forgets the records instead of failing when the directory is
  already gone. The dry run stays a pure read and keeps answering `missing`, which
  is what makes the dialog offer the removal. `POST`/`GET
  /api/lm/{prefix}/forget-folder` is the endpoint for a node that maps to no
  directory at all (the GET form is for the browser extension, which is GET-only).
* The sidebar falls back to it from the delete flow, offers "Remove from list" in
  the missing state, and reports the folder as removed from the sidebar rather than
  as a delete that never happened. An `exists` conflict says the directory is back
  and should be deleted instead.

Verified: 3811 backend tests, 1543 JS tests, 96 Vue tests, 20 i18n tests.
This commit is contained in:
Will Miao
2026-10-12 09:31:29 +08:00
parent 0508daa0fb
commit 3a718ce2c3
19 changed files with 432 additions and 18 deletions
+48 -3
View File
@@ -589,6 +589,33 @@ class ModelMoveService:
return rel.replace(os.sep, "/")
return ""
async def forget_folder(self, folder: str) -> Dict[str, Any]:
"""Drop the records of a folder that is on disk under no root (#1145).
A directory moved or deleted with a file manager can leave the sidebar
holding a node no delete can clear: the folder is gone, so there is
nothing to remove and every attempt answered "Folder no longer exists".
This drops what remains — the recorded folder entry and the cached model
rows under it — and is refused while any root still holds the directory,
because then the caller wants a delete, not a cleanup.
"""
resolution = self.resolve_folder(folder)
if not resolution.get("success"):
return resolution
normalized = resolution.get("folder") or ""
if not normalized:
return {"success": False, "error": "Folder is required"}
if resolution.get("candidates"):
return {
"success": False,
"code": "exists",
"error": "The folder still exists on disk",
}
await self._forget_folder(normalized)
return {"success": True, "folder": normalized}
def resolve_folder(self, folder: str) -> Dict[str, Any]:
"""Map a library-relative folder onto the directories it stands for.
@@ -685,11 +712,29 @@ class ModelMoveService:
}
if not os.path.isdir(absolute_path):
# `missing` is its own code so the sidebar can tell "this node's
# directory is gone, refresh" apart from a failed operation.
# directory is gone" apart from a failed operation. There is
# nothing left to delete, but the sidebar can still be holding the
# node: a folder moved or removed with a file manager leaves its
# records behind, and "Folder no longer exists" was a dead end --
# the ghost could not be cleared from the UI at all (issue #1145).
# The real delete therefore forgets those records and reports
# success; the dry run stays a pure read and keeps answering
# `missing`, which is what makes the dialog offer the removal.
if dry_run:
return {
"success": False,
"code": "missing",
"error": "Folder no longer exists",
}
relative_folder = self._calculate_relative_folder(absolute_path)
await self._forget_folder(relative_folder, absolute_path)
return {
"success": False,
"success": True,
"code": "missing",
"error": "Folder no longer exists",
"already_missing": True,
"folder": relative_folder,
"folder_path": absolute_path.replace(os.sep, "/"),
}
if self._is_model_root(absolute_path):