-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Do not detect clone entry as duplicated content. #379
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #379 +/- ##
==========================================
- Coverage 28.00% 27.93% -0.08%
==========================================
Files 26 26
Lines 2582 2585 +3
Branches 1373 1376 +3
==========================================
- Hits 723 722 -1
- Misses 1375 1376 +1
- Partials 484 487 +3 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the functionality point of view it should work, but I have a couple of comments regarding the performance impact of this fix.
@mgautierfr Now that libzim |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase-fixup while addressing the last comment and the PR can be merged.
3a1b0ff
to
5fc96aa
Compare
Last comment fixed. |
If two entries point to the same tuple (cluter_id, blob_id), we must not report them as duplicated content.
5fc96aa
to
f3d38b3
Compare
CI for packages on debian unstable is failing because of a wrong version of libzim available. |
Fix #377 |
If two entries point to the same tuple (cluter_id, blob_id), we must not report them as duplicated content.
Depends of openzim/libzim#833
Missing: Test of the check with a zim file actually containing clone entries.