You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a particular buffer zipped over the variable itself. Data becomes corrupted. Possible to occur up to version 20. Need checking
If it is zipped to a new variable , everything works as expected
buffer.json='https://www.dropbox.com/s/g7jh19o0cmn9kp3/buffer.json?dl=0';letbuffer=Buffer.from(buffer.json)//Pseudo code here. Parse it however you likebuffer=zlib.gzipSync(buffer);zlib.unzipSync(buffer)//Error: incorrect data check
How often does it reproduce? Is there a required condition?
Always. Consistent
What is the expected behavior? Why is that the expected behavior?
using this will only say that you ignore the integrity checks at the end of the stream / buffer to make sure that the data you got out was the expected end result
Tried but no luck. Strange part is , i have zipped twice totally same data. . However one of them fails to unzip and other one succeeds. When inspected byte by byte as a buffer errored one writes a byte value as 210 instead 218 in the middle of the buffer (11040 or so of total 24000 bytes)
Activity
jimmywarting commentedon May 15, 2023
Related: nodejs/undici#2123?
MuhammedKalkan commentedon May 15, 2023
Maybe i should add , if it is zipped to a new variable , everything works as expected
jimmywarting commentedon May 15, 2023
try with this option:
MuhammedKalkan commentedon May 15, 2023
I want to read whole data by the way. Documentation says only part could be read with that options?
I use it to de/compress an important data.
jimmywarting commentedon May 15, 2023
using this will only say that you ignore the integrity checks at the end of the stream / buffer to make sure that the data you got out was the expected end result
MuhammedKalkan commentedon May 16, 2023
Tried but no luck. Strange part is , i have zipped twice totally same data. . However one of them fails to unzip and other one succeeds. When inspected byte by byte as a buffer errored one writes a byte value as 210 instead 218 in the middle of the buffer (11040 or so of total 24000 bytes)
Just try this file : https://www.dropbox.com/s/p1zvp64x5kjell1/test?dl=0
MuhammedKalkan commentedon May 17, 2023
Closing this one, might be os or memory error