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
Today, I've noticed that while removing a directory T:\Temp\Rider2023.1 (18.49 GiB), Vacuum has deleted it entirely, and not moved to the recycle bin.
Some hypothesis on what could cause that behavior:
the directory is too big to be put into the recycle bin
some files are too big
some paths are too long
Normally, Windows Shell will ask the user what to do, but it's possible that some flags we are passing to it lead to just deleting the directory in case of questions.
Deserves further investigation.
The text was updated successfully, but these errors were encountered:
$ md T:\Temp\vac-wsp
$ cd T:\Temp\vac-wsp
$ fsutil file createnew test 18000000000 # creates a file of 18 GB in size
$ vacuum -d T:\Temp\vac-wsp # deletes the file without putting it into the recycle binRemoving file T:\Temp\vac-wsp\test… ok
Alright, the current plan will be to use IFileOperation manually (perhaps extract it into a reusable library later), and try handling the results.
Ideally, we'd want to properly handle the deletion states: by default, do not delete such a file and properly detect the status, and only force-delete it if called with --force.
Today, I've noticed that while removing a directory
T:\Temp\Rider2023.1
(18.49 GiB), Vacuum has deleted it entirely, and not moved to the recycle bin.Some hypothesis on what could cause that behavior:
Normally, Windows Shell will ask the user what to do, but it's possible that some flags we are passing to it lead to just deleting the directory in case of questions.
Deserves further investigation.
The text was updated successfully, but these errors were encountered: