Open r614 opened 7 months ago
Here is the problem: https://github.com/oven-sh/bun/issues/5091
experiencing this also with:
@sentry/bun version 7.93.0
bun version 1.0.20
Can I ask, is this an issue with the Sentry SDK, like does it work if you remove/disable Sentry?
Can I ask, is this an issue with the Sentry SDK, like does it work if you remove/disable Sentry?
Disabling sentry fixes the issue for me (commenting out Sentry.init or adding this line to the Sentry.init config object: integrations: (int) => int.filter((i) => !["BunServer", "Http"].includes(i.name)),
- as shown in the original issue)
The response on the relevant sentry issue was that since their monkey patching works for node that this must be an issue with bun
Hello! Thanks for all of your hard work. @Jarred-Sumner I think lots of teams are eager to move to Bun but can't due this issue, do you know when we can expect a fix for this? 🥲 Thanks again!
We changed how we do monkeypatching of HTTP in our upcoming new Sentry JavaScript SDKs major version, 8.0.
Currently there is a beta release: https://github.com/getsentry/sentry-javascript/releases/tag/8.0.0-beta.1
This means you can use Sentry with the v8 beta and tracing should work with Bun!
Fixed with 8.0.0 of @sentry/bun
- please give it a try. Thanks!
https://docs.sentry.io/platforms/javascript/guides/bun
https://docs.sentry.io/platforms/javascript/guides/bun/migration/v7-to-v8
@AbhiPrasad Does this use the latest changes from v1.1.8?
@AbhiPrasad Does this use the latest changes from v1.1.8?
Yes!
PR here: https://github.com/getsentry/sentry-javascript/pull/11960
What version of Bun is running?
1.0.7+b0393fba6200d8573f3433fb0af258a0e33ac157
What platform is your computer?
Darwin 23.1.0 arm64 arm
What steps can reproduce the bug?
Ref: https://github.com/getsentry/sentry-javascript/issues/9564 and https://github.com/getsentry/sentry-javascript/issues/9608
Code Sample
index.ts
files.ts
package.json
What is the expected behavior?
File is uploaded to S3 successfully, action is logged to Sentry.
What do you see instead?
Request is never completed. It doesn't timeout either, just keeps the client waiting. AFAIK I understand it, the S3 client doesn't even get a response so not sure if the file upload request is even sent.
Logs:
Additional information
Seems like a Bun issue from https://github.com/getsentry/sentry-javascript/issues/9564#issuecomment-1841082305 Removing the HTTP integration from Sentry fixes the issue for now, but we lose some logs we really need