Kris Zyp
Kris Zyp
Ok, these updates are published in v2.3.8.
@pieh A few questions about this: Are you thinking this is the same issue (reported in same place) as #153 (just with better error messaging)? You don't think this is...
So to summarize my understanding of potential causes of bad reader slots: - If multiple database instances are opened for the same database file, one instance can clear reader slots...
I think this is a potentially useful clue. It is actually challenging to conceive of how this type "out of range" error could occur; I have never seen it before...
Published version v2.4.0 with changes to address the dbi "out of range" error.
You aren't by any chance using any `readOnly` databases are you?
I still don't have any ideas for how this could occur. I think this error would be the result of using an old read transaction to access a database that...
Its a safe, minor patch and version numbers are cheap, so went ahead and published this v2.4.3.
And just FYI, as far as how to directly use the source/compile, I think you would set a package version override, and directly use a commit/branch, like `"lmdb": "DoctorEvidence/lmdb-js#"`. With...
I have been able to create a test case that reproduces this error. For me this occurs when there are a large number of async writes or async transactions running...