Ward Peeters

I can still reproduce this error with ``` [email protected], [email protected], lmdb@^2.0.2, lmdb@^2.2.6, lmdb@^2.4.2: version "2.4.2" resolved "https://registry.yarnpkg.com/lmdb/-/lmdb-2.4.2.tgz#eefd082ac3570bca88a8f149df12ea20fbf40b29" integrity sha512-dgqoGgHl/lzPobumxIsagVy7JXBAdFJv74avJTC733lb6d/RiCrzjm5YOUyCjhKnCNTNlNPGBP6/C1gZelUwlA== dependencies: msgpackr "^1.5.4" node-addon-api "^4.3.0" node-gyp-build-optional-packages "5.0.2" ordered-binary "^1.2.4" weak-lru-cache "^1.2.2"...

No, we initiate multiple caches per plugin: https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/utils/cache-lmdb.ts ``` private static getStore(): RootDatabase { if (!GatsbyCacheLmdb.store) { GatsbyCacheLmdb.store = open({ name: `root`, path: path.join(process.cwd(), `.cache/${cacheDbFile}`), compression: true, maxDbs: 200, })...

If you can publish a canary, I'm happy to do so or if you have a guide how to compile myself that's helpful too

Still getting an error with 1.4.5 - I disabled all child_procs from spawning so it's a single process ``` 13:51:31 PM: err: Error: Invalid argument: The dbi 10 was out...

Yeah it could definilty be the case. We can open the cache earlier, now we open it on first write.

@kriszyp can I try your latest commit or isn't that the full fix yet?

No need to apologize :) We're very grateful for your work here! 🥇

This is the error message I get with the 2.3.0 beta Error message ``` There was an error in your GraphQL query: MDB_PROBLEM: Unexpected problem - txn should abort: mdb_page_unspill...

I'll see if I can get you a repro. We're not using childTransactions and I don't event think we're using any transactions ourselves.

Sadly I do not use Wsl. Also wsl2 isn't available yet for me. I can give wsl v1 another go, it worked in the past