when sz in linux, crc32 failed
See original GitHub issueexception:
Uncaught Error: CRC check failed! (got: 97,49,55,32; expected: 99,203,3,169)
at a (zmodem.js:1)
at Object.verify32 (zmodem.js:1)
at i (zmodem.js:1)
at Function.parse (zmodem.js:1)
at r.Session.Receive._parse_and_consume_header (zmodem.js:1)
at r.Session.Receive._consume_first (zmodem.js:1)
at r.Session.Receive.consume (zmodem.js:1)
at t.Sentry.consume (zmodem.js:1)
at WebSocket.handleWSMessage (zmodem.ts:75)
lrzsz version:
sz (lrzsz) 0.12.21rc
but use sz -e is ok
sz -h
-e, --escape escape all control characters (Z)
so, i think when your crc, include control charaters?
can you fix it. Thank you~!~
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
How to calculate crc32 checksum from a string on linux bash
Just to provide some technical details, gzip uses crc32 in the last 8 bytes and the -c option causes it to output to...
Read more >Command to verify CRC (CRC32) hashes recursively
Let say we have stored crc32 values in file in the same format like ... if [ "${line% \**}" == "$crc32" ] then...
Read more >Why does rsync use MD5 instead of CRC-32? : r/linux - Reddit
Seems like a total waste of resources when doing backups. md5 was never mean't for this and takes a much greater amount of...
Read more >SAS Zip Engine Problem - CRC32 Checksum Error
Background I'm running SAS 9.4 M6 on a Windows Server 2016 Standard (64 bit) machine. I'm trying to update and add some xml...
Read more >undefined reference to 'crc32' ? - No comment
+ * crc32.h + * See linux/lib/crc32.c for license and changes ... split fail: 0x%08x\n", crc2); + } + + return crc1; +}...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I pushed a fix for the array_buf issue.
@yumaojun03 As it happens, while digging into this I realized that there were no tests that actually flex the “happy path” in receive transfers. Worse, I realized that some of tests I did have failed reliably but weren’t even running because of a bug in another test.
So, I’ll roll fixes for all of these into a new release.