Web UI check -chunks includes -a option, overriding -id option

Please describe what you are doing to trigger the bug:

Schedule check job with -id Joint and -chunks options in Web UI

Please describe what you expect to happen (but doesn’t):

Expect chunks only in specified snapshot id to be verified.

Please describe what actually happens (the wrong behaviour):

Chunks in all snapshots are verified.

Running check command from /share/CACHEDEV1_DATA/.qpkg/Duplicacy/.duplicacy-web/repositories/localhost/all
Options: [-log check -storage NAS0 -id Joint -chunks -a -tabular]
2020-12-02 07:59:29.353 INFO STORAGE_SET Storage set to /share/TR-004/Duplicacy/storage
2020-12-02 08:00:02.252 INFO SNAPSHOT_CHECK Listing all chunks
2020-12-02 08:00:44.652 INFO SNAPSHOT_CHECK 18 snapshots and 565 revisions
2020-12-02 08:00:44.764 INFO SNAPSHOT_CHECK Total chunk size is 2038G in 446030 chunks
2020-12-02 08:00:44.789 INFO SNAPSHOT_CHECK All chunks referenced by snapshot Test at revision 1 exist
2020-12-02 08:00:44.789 INFO SNAPSHOT_CHECK All chunks referenced by snapshot Test at revision 2 exist
2020-12-02 08:00:44.811 INFO SNAPSHOT_CHECK All chunks referenced by snapshot Test at revision 3 exist

2020-12-02 08:12:05.219 INFO SNAPSHOT_VERIFY Verifying 446027 chunks
2020-12-02 08:12:05.931 INFO VERIFY_PROGRESS Verified chunk bff57f26d1322e792c5655a4d404de79b13511cc6c19ff94a36727e3a952e686 (1/446027), 19.66MB/s 3 days 16:14:07 0.0%
2020-12-02 08:12:05.989 INFO VERIFY_PROGRESS Verified chunk 8d923952a71cb1f6180692f8716f39c28088a470f97e8d5d6197cd71097f9505 (2/446027), 21.17MB/s 1 day 23:43:53 0.0%
2020-12-02 08:12:06.081 INFO VERIFY_PROGRESS Verified chunk 42e1b8ad24a6178af8a6d315d2ec133d5640d472a25aa4750ec219fb498665fe (3/446027), 22.83MB/s 1 day 11:35:29 0.0%

2020-12-03 06:11:21.573 INFO VERIFY_PROGRESS Verified chunk 7c5f35032337bc73b4b176d37f47f3f83fecccd6835ee85b7727ca7fb3833aca (446027/446027), 28.32MB/s 00:00:00 100.0%
2020-12-03 06:11:21.607 INFO SNAPSHOT_VERIFY All 446027 chunks have been successfully verified
2020-12-03 06:11:24.412 INFO SNAPSHOT_VERIFY Added 446027 chunks to the list of verified chunks

I’ll fix this in the coming release.

+1 on this because the check command isn’t very memory efficient and running it with -a causes the process to be killed with oom exceptions.
I’m hoping that running check on each id sequentially will reduce memory usage to the point that it can complete.

Thanks for fixing this in the latest WebUI! My checks were running out of memory, but now I can run them separately and get through all of them.
The real root cause for needing the ability to run checks separately is the memory issue. I looked at the code and think you can cut the memory needed by check in half. I posted the fix here: Suggested fix for massive memory usage in "check"

Thanks!