You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 12, 2023. It is now read-only.
I happened to delete a TileDB workspace directory with a normal rm. It still appeared in the output from tiledb_ls_workspaces but any calls to that workspace gave an error including trying to create the workspace again. In the end, I ended up deleting .tiledb which probably shouldn't be the solution very often. Would it make sense to have a function that brings .tiledb into a "correct" state or how should I handle the situation after a folder has been deleted outside TileDB.
I happened to delete a TileDB workspace directory with a normal
rm. It still appeared in the output fromtiledb_ls_workspacesbut any calls to that workspace gave an error including trying to create the workspace again. In the end, I ended up deleting.tiledbwhich probably shouldn't be the solution very often. Would it make sense to have a function that brings.tiledbinto a "correct" state or how should I handle the situation after a folder has been deleted outside TileDB.