-
Notifications
You must be signed in to change notification settings - Fork 128
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
Combining --progress and --replay deletes hashes in rmlint.json #581
Labels
Comments
This isn't explicitly documented, but it is subtly implied by the way --progress is described in the manpage:
Note the explicit -o clears the default outputs, which are different in replay mode. But --progress still allows you to override the sh/json outputs individually. I agree that this behavior is confusing, and I am preparing a pull request that simplifies the option. |
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Aug 5, 2022
The behavior of --progress could be surprising, especially when combined with --replay. Simplify its meaning and make sure the docs describe it accurately. Fixes sahib#581
mb720
changed the title
Combinining --progress and --replay deletes hashes in rmlint.json
Combining --progress and --replay deletes hashes in rmlint.json
Aug 6, 2022
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Aug 7, 2022
The behavior of --progress could be surprising, especially when combined with --replay. Simplify its meaning and make sure the docs describe it accurately. Fixes sahib#581
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Sep 18, 2022
The behavior of --progress could be surprising, especially when combined with --replay. Simplify its meaning and make sure the docs describe it accurately. Fixes sahib#581
intelfx
pushed a commit
to intelfx/rmlint
that referenced
this issue
Mar 9, 2023
The behavior of --progress could be surprising, especially when combined with --replay. Simplify its meaning and make sure the docs describe it accurately. Fixes sahib#581
intelfx
pushed a commit
to intelfx/rmlint
that referenced
this issue
Mar 9, 2023
The behavior of --progress could be surprising, especially when combined with --replay. Simplify its meaning and make sure the docs describe it accurately. Fixes sahib#581
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi and thanks for rmlint!
I was surprised by the behavior of this command:
I expected that rmlint would reuse the existing rmlint.json and create a
rmlint.replay.sh
that makes hardlinks out of duplicate files. And report a bit of progress while doing so.Instead, both rmlint.json and rmlint.sh got overwritten with nearly empty files. The hashes are gone from rmlint.json.
I wasn't sure what was wrong and didn't expect that the innocuous looking
--progress
option was causing trouble. But it was. Removing--progress
made rmlint behave as I wanted:I somehow suspect this behavior is a bug since rmlint overwrites data without warning and it doesn't seem to be documented in the man page.
I'm using rmlint 2.10.1 on Arch Linux, compile features are according to
rmlint --version
The text was updated successfully, but these errors were encountered: