`check -tabular` does not use `-all`

Continuing the discussion from How to investigate growing size?:

@Droolio raised this and i also tested:

  • duplicacy check -stats implies -all however
  • duplicacy check -tabular does not imply -all.

Is this a docs bug, or a duplicacy bug?

1 Like

I’ve confirmed this is still an issue in 2.2.3. Though at this point it seems like it might make more sense to update the documentation since the GUI seems to be written based around the current behavior.

% duplicacy check -tabular
Storage set to /Users/test/Desktop/storage
Listing all chunks
1 snapshots and 1 revisions
Total chunk size is 546 in 7 chunks
All chunks referenced by snapshot test1 at revision 1 exist

  snap | rev |                          | files | bytes | chunks | bytes | uniq | bytes | new | bytes |
 test1 |   1 | @ 2019-11-23 08:02 -hash |     1 |     2 |      4 |   279 |    4 |   279 |   4 |   279 |
 test1 | all |                          |       |       |      4 |   279 |    4 |   279 |     |       |

% duplicacy check -tabular -all
Storage set to /Users/test/Desktop/storage
Listing all chunks
2 snapshots and 2 revisions
Total chunk size is 546 in 7 chunks
All chunks referenced by snapshot test1 at revision 1 exist
All chunks referenced by snapshot test2 at revision 1 exist

  snap | rev |                          | files | bytes | chunks | bytes | uniq | bytes | new | bytes |
 test1 |   1 | @ 2019-11-23 08:02 -hash |     1 |     2 |      4 |   279 |    3 |   267 |   4 |   279 |
 test1 | all |                          |       |       |      4 |   279 |    3 |   267 |     |       |

  snap | rev |                          | files | bytes | chunks | bytes | uniq | bytes | new | bytes |
 test2 |   1 | @ 2019-11-23 08:02 -hash |     1 |     2 |      4 |   279 |    3 |   267 |   4 |   279 |
 test2 | all |                          |       |       |      4 |   279 |    3 |   267 |     |       |

@gchen what’s your take on this?

I think -tabular should imply -all too. I’ll fix this in the coming release.

5 Likes

This was fixed in 2.3.0 (released last night)!

1 Like

This topic was automatically closed after 35 days. New replies are no longer allowed.