-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Correctly test invalid offsets in clusters. #895
Conversation
a5d1c2f
to
0888639
Compare
@mgautierfr Both macOS and Windows CI don't pass. |
0888639
to
58a727b
Compare
I know. |
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.
LGTM. Can be merged once rebased & fixed-up.
@mgautierfr What is the status here? Testing auite has been released, but the CI still fails... and acutally I wanted to release 9.2.2 this WE. |
58a727b
to
b1c15dc
Compare
This test is to check that value parsed are consistent. This is not to catch a potential bug in our code. So we must throw a ZimFileFormatError in this case.
Not that the test is correctly catching invalid offset only for nons variant. Current `validate` method is not checking the offsets in the cluster. Nons variant detect the invalid offset as `titlePtrList` is stored in the cluster and so we try to open it (using `X/listing/titleOrdered/vX`) Correct test will be added in next commit. Need PR openzim/zim-testing-suite#9
b1c15dc
to
338812a
Compare
338812a
to
14fdd56
Compare
I have:
I will merge |
This offset test in the cluster is to check that value parsed are consistent.
This is not to catch a potential bug in our code.
So we must throw a ZimFileFormatError in this case.
Extend the
validate
function to test this kind of corrupted offset.Need openzim/zim-testing-suite#9
Fix #893