Closed vladar closed 3 years ago
Do you have any idea what the (serialized) object is that might be triggering the error?
I am trying to reproduce it but it's tricky as data comes from an external source and I have to wait a while to retry. I will report back when the next build finishes (or fails)
I've narrowed it down to the serialized value in the attached tmp.txt file. It fails with this simple script:
const fs = require("fs")
const { unpack } = require("msgpackr")
const bin = fs.readFileSync(`./tmp.txt`)
const result = unpack(bin) // throws here
Although I am not sure if it is an issue with unpacking or actually packing.
Thank you for the excellent test case. This should now be fixed in msgpackr v1.3.1, but I'll get a proper lmdb-store release that depends on it out soon (have some other things I am wrapping up with it).
Ok, should be fixed in v1.5.0.
Yup, seems to be working fine. Thanks!
I am seeing this error in one of my tests with
lmdb-store
:It happens when I run the following code:
So it lazily iterates all items in a database by key and fetches values by this key. But then at some point, it fails with this
msgpackr
error.