Open atbe opened 4 months ago
I believe this was fixed with https://github.com/oven-sh/bun/issues/13736 and other timeout related fixes, can you see if still reproduces after bun upgrade --canary
?
Hi, still having this issue, even in canary
christopy@MacBook-Pro-de-Christopher new-fintech % bun dev
$ bun run --watch src/index.ts
🦊 Elysia is running at localhost:9999
180 | timeout = setTimeout(() => {
181 | const removed = this.removeQueue(i, _args);
182 | if (removed) {
183 | const message = 'Operation `' + this.name + '.' + i + '()` buffering timed out after ' +
184 | bufferTimeoutMS + 'ms';
185 | const err = new MongooseError(message);
^
MongooseError: Operation `accounts.findOne()` buffering timed out after 10000ms
at new MongooseError (1:23)
at /Users/christopy/code/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185:23
Bun version:
1.1.34
What version of Bun is running?
1.1.17+bb66bba1b
What platform is your computer?
Linux 6.6.31-linuxkit x86_64 unknown
What steps can reproduce the bug?
When attempting to use
mongoose
at runtime withbun
, we run into the error. We swapbun
fortsx
and there's no error. We'll try to isolate the code-path to understand exactly what call is causing the timeout.What is the expected behavior?
That the program operates normally, and all
mongoose
calls succeed.What do you see instead?
We see the following runtime error:
Additional information
No response