-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Wrong data returned from getitem (DeepState fuzzing) #95
Comments
It looks like the key to this is:
byte 129 will be a 1 in "items" and a 0 in the original data As far as I can tell, this is a real bug, don't see any likely API violations |
The same tests all pass on the original cblosc, which strongly suggests this is a cblosc2 bug. |
is a standalone test showing the problem.
|
@FrancescAlted you might want to take a look at this; not an API meaning issue, but a data-changing bug not present in old blosc. |
Standalone test case doesn't need deepstate. |
@FrancescAlted Do you have an ETA on a bug fix for this? |
I am pretty swamped lately, but will try to find some time for this during the holidays season. No guarantees though, so any help is appreciated indeed. |
Would more details about when it happens be helpful? The code looks non-trivial to dive into to bugfix/root cause, but I can clarify conditions quite a bit I suspect... |
@FrancescAlted did you ever get a chance to confirm the bug here, if not yet to fix? |
Yup, it took me a while, but the problem was finally fixed. Thank you for following on this one! |
Great! Will retest today! |
This is a minimal test case; making any value smaller causes it to pass.
The text was updated successfully, but these errors were encountered: