Skip to content
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

Closed
victor opened this issue Jun 30, 2021 · 6 comments

Comments

@victor
Copy link

victor commented Jun 30, 2021

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

@aonez
Copy link
Owner

aonez commented Jul 2, 2021

It's set to only remove files if the operation works properly. I'll test if a disk full error bypasses somehow this.

@aonez aonez self-assigned this Jul 2, 2021
@aonez aonez added the core label Jul 2, 2021
@aonez aonez added this to the Look at milestone Jul 2, 2021
@aonez
Copy link
Owner

aonez commented Jul 2, 2021

@victor what format and setting were you using?

@no-response no-response bot closed this as completed Jul 9, 2021
@aonez aonez reopened this Jul 11, 2021
@no-response no-response bot closed this as completed Jul 11, 2021
@aonez aonez reopened this Jul 11, 2021
@aonez aonez modified the milestones: Look at, 1.2.16 Jul 11, 2021
@victor
Copy link
Author

victor commented Jul 12, 2021

Format was 7z, with slow, max compression.

@aonez aonez added the bug label Jul 12, 2021
Repository owner deleted a comment from no-response bot Jul 12, 2021
Repository owner deleted a comment from no-response bot Jul 12, 2021
@aonez aonez closed this as completed Jul 12, 2021
@aonez
Copy link
Owner

aonez commented Jul 12, 2021

I've detected the issue, fixed for next revision, coming in a few. Thanks a lot @victor!

@aonez aonez added the fixed label Jul 12, 2021
@victor
Copy link
Author

victor commented Jul 12, 2021 via email

@aonez
Copy link
Owner

aonez commented Jul 15, 2021

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants