Skip to content

Conversation

@Cyan4973
Copy link
Contributor

@Cyan4973 Cyan4973 commented Dec 18, 2025

This is a bug in the streaming implementation of the v0.5 decoder. The bug has always been there.
It requires an uncommon block configuration, which wasn't tested at the time.

v0.5 is deprecated now,
latest version to produce such format is v0.5.1 from February 2016. It was superseded in April 2016.
So it's both short lived and very old.

Another PR (#4554) will remove support of this format by default,
but it will still be possible to explicitly request this support on demand, hence better fix the issue.

Fix #4553

This is a bug in the streaming implementation of the v0.5 decoder.
The bug has always been there.
It requires an uncommon block configuration, which wasn't tested at the time.

v0.5 is deprecated now,
latest version to produce such format is v0.5.1 from February 2016.
It was superceded in April 2016.
So it's both short lived and very old.

Another PR will remove support of this format,
but it will still be possible to explicitely request this support on demand,
so better fix the issue.
@Cyan4973 Cyan4973 self-assigned this Dec 18, 2025
@Cyan4973 Cyan4973 added the bug label Dec 18, 2025
@meta-cla meta-cla bot added the CLA Signed label Dec 18, 2025
@Cyan4973 Cyan4973 merged commit e00ddf6 into dev Dec 19, 2025
105 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Legacy v0.5 streaming decompression produces different bytes than one-shot API

2 participants