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
After the upgrade from a quite stale version of @sentry/serverless I noticed that I can't catch the exceptions from my cloud functions in tests. I've read through the sources and found the following code:
As I understand, this then(...) throws an error that can't be catched by the caller because it is handled in a different step of an event loop. Does it look like a bug? Wouldn't it be better to return on line 131?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After the upgrade from a quite stale version of
@sentry/serverless
I noticed that I can't catch the exceptions from my cloud functions in tests. I've read through the sources and found the following code:https://github.com/getsentry/sentry-javascript/blob/7.87.0/packages/serverless/src/gcpfunction/http.ts#L130-L137
As I understand, this
then(...)
throws an error that can't be catched by the caller because it is handled in a different step of an event loop. Does it look like a bug? Wouldn't it be better to return on line 131?Beta Was this translation helpful? Give feedback.
All reactions