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
Hello, currently we've been facing some issues with Sentry and Nest Raven. Due to a change Sentry did some months ago all errors caught by Nest Raven and sent to Sentry were causing an error due to this issue so as a workaround we used a fixed version of @sentry/node that does not have this issue 5.23.0.
Yesterday they upgraded the library with the fix that solves the mentioned issue @sentry/[email protected], but because we use Sentry via Nest Raven to report errors, we are still having that issue because Nest Raven keeps using @sentry/[email protected]. By checking Sentry's changelog the upgrade to v6 does not bring breaking changes.
The text was updated successfully, but these errors were encountered:
Hello, currently we've been facing some issues with Sentry and Nest Raven. Due to a change Sentry did some months ago all errors caught by Nest Raven and sent to Sentry were causing an error due to this issue so as a workaround we used a fixed version of
@sentry/node
that does not have this issue5.23.0
.Yesterday they upgraded the library with the fix that solves the mentioned issue
@sentry/[email protected]
, but because we use Sentry via Nest Raven to report errors, we are still having that issue because Nest Raven keeps using@sentry/[email protected]
. By checking Sentry's changelog the upgrade to v6 does not bring breaking changes.The text was updated successfully, but these errors were encountered: