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.
Failed decode with large binary data
See original GitHub issueHi,
There is an issue when I try to encode/decode a larger Buffer data. The same data works with MsgPack.
I made a repro example on repl.it: https://replit.com/@icebob/cbor-issue#index.js
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Getting a FileSystemException when reading text file
This probably means that your file contains binary data that is not valid ASCII or UTF-8. You can try LATIN1 and see if...
Read more >unexpected EOF - large binary file (>1mb and <10mb)
I've run my own mongo instances used a json file that adds the document to the collection and then used golang to read...
Read more >dp:binary-decode truncates large part of binary base64 ... - IBM
The issue is that the binary decode truncates a large part of the string. Is there an other way to extract the binary...
Read more >Open Dataset Character Encoding Error with binary file ...
Reason for the error is unix server uses big endian format while preparing binary file, where as linux server uses little endian format...
Read more >encoding/binary - Go Packages
Package binary implements simple translation between numbers and byte sequences and encoding and decoding of varints.
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 Free
Top 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
OK, thanks for the great test case, there are some fixes I am working on porting over, so will make sure they address this issue.
I believe this should be fixed in v0.8 (let me know if you still see the issue).