-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(core): Fix error handling when sending envelopes #17662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
size-limit report 📦
|
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
0c53b6b
to
23b3d40
Compare
23b3d40
to
42bc9f0
Compare
I noticed that we actually handled errors in
sendEnvelope
incorrectly - we would resolve this function with the rejection reason, if sending fails. this does not match the type ofTransportMakeRequestResponse
, you could actually get something like this out (and the tests actually incorrectly tested this):This PR fixes this to instead resolve with an empty object (which matches the expected return type).
Extracted this out of #17641 because it is actually a bug/fix.