Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Calling `inflate` on data created from `Pako.deflate` returns `(null, null)`
See original GitHub issueIssue Description
Some observations that I noted:
inflate fails with (null, null)
inflateSync fails with EOF:
This is probably the most important problem since one would expect either data or an error.
decompress works fine:
deflateSync : incorrect header check
It appears as though Pako has a different idea of what constitutes inflate / deflate i.e.
gzipSync: seems to correspond to pako.inflate
I noted that the builtin CompressionStream seems to correlate with what Pako does i.e. 'inflate' algorithm for Pako and CompressionStream seem to be the same.
zlib: same as gzip
zip: fails, same as deflate
Summary
I’ve no idea what’s going on here (and the issues observed may be with Pako), but I hope the above is useful feedback.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
v0.7.0 is released and this bug should be fixed, along with the improved errors from #54.
I found and fixed the bug; will be out in v0.7.0.