-
Notifications
You must be signed in to change notification settings - Fork 168
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
Unit test regression after 1.5.2 - ZstdIOException: Unknown frame descriptor #301
Comments
Can you check with the versions between 1.5.2 and 1.5.5-11, e.g. can you check with 1.5.4-2 and 1.5.5-1? |
I tried git-bisect style with multiple versions >= 1.5.2 until I figure out that 1.5.2 was the last one working. But I can make a full compatibility test with all versions if this helps you. |
That's strange. We have unit tests that assure that can still decompress payloads compressed with zstd-0.4 version. So breakage in the format is surprising. Can you extract the compressed payload and decompress it with the CLI zstd to see if it fails or not? |
Surprisingly I can not, even with older Zstd cli versions. But our decompression is working for years with apache commons compress for decompression -.- It detects the magic bytes (I see it in debugging) otherwise it wouldn't call zstd-jni code. Also the compression code is quite simple but in Rust -> link |
Can you send me an example compressed message (could be with the JSON header) that shows that problem to try to find the issue? |
The file is in the repo, direct download here: To get the raw zstd stream I just went for Thank you for taking the time. ❤️ |
After trying to upgrade all of our dependencies this test fails on all newer versions after 1.5.2 with the error
com.github.luben.zstd.ZstdIOException: Unknown frame descriptor
.The compressed zstd bytes in the file have been created with a much older version, but I can't tell you which one. This matches our production scenario where we also have these older files.
What be nice if someone can look into it. Thank you.
You can checkout this dependabot branch to run it yourself.
The text was updated successfully, but these errors were encountered: