-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When there is an error while compressing, original files should not be sent to the Bin #885
Comments
It's set to only remove files if the operation works properly. I'll test if a disk full error bypasses somehow this. |
@victor what format and setting were you using? |
Format was 7z, with slow, max compression. |
I've detected the issue, fixed for next revision, coming in a few. Thanks a lot @victor! |
glad to be of service
Enviat des del meu iPhone
… El 12 jul 2021, a les 18:22, aONe ***@***.***> va escriure:
I've detected the issue, fixed for next revision, coming in a few. Thanks a lot @victor!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@victor, as a followup: This should be fixed in the upcoming 1.2.16. Test build: Keka-1.2.16.r4608.7z There was an issue detecting the error codes that has been reported in various ways (#891 #885). Thanks a lot for the feedback! |
I encountered a disk full error when compressing some folders, with the option to move the original files to the Bin after compression. This option should only be honored on successful compression, to avoid data loss and an easier retry.
One could argue that the files in the Bin are not lost and the can be recovered easily, but that is not entirely true: there may be many similarly named files in the bin and finding the correct ones may prove complicated. Also, one of the first things one can do irreflexively (meaning, I did it) is to empty the Bin, to gain disk space. Doing this ensures there's no trace of the original source files to retry compression after gaining some disk space
The text was updated successfully, but these errors were encountered: