You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
What steps will reproduce the bug?
Bun.serve({fetch(this,request){consttime=Date.now();setTimeout(()=>{Bun.write(Bun.stdout,`Resolved in ${Date.now()-time} \n`);},1000);returnnewResponse("OK");},port: 3005,});
How often does it reproduce? Is there a required condition?
This example reproduces consistently
What is the expected behavior?
Resolved in 1000
Resolved in 1000
Resolved in 1000
Resolved in 1000
Resolved in 1000
What do you see instead?
When requests are launched via scripts, or by hand in rapid succession
Resolved in 1001
Resolved in 586
Resolved in 66
Resolved in 1000
Resolved in 1001
Additional information
In a more complex cases I noticed that setTimeouts may resolve instantly or not resolve at all, instead of set period of ms. If I manage to reduce the repro to manageable format I will add it in a comment. From what I noticed the issue only appears when setTimeout is used with Bun server
The text was updated successfully, but these errors were encountered:
Version
0.1.2
Platform
Linux 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
This example reproduces consistently
What is the expected behavior?
What do you see instead?
When requests are launched via scripts, or by hand in rapid succession
Additional information
In a more complex cases I noticed that setTimeouts may resolve instantly or not resolve at all, instead of set period of ms. If I manage to reduce the repro to manageable format I will add it in a comment. From what I noticed the issue only appears when setTimeout is used with Bun server
The text was updated successfully, but these errors were encountered: