Skip to content

Conversation

st0012
Copy link
Collaborator

@st0012 st0012 commented Dec 10, 2020

Because ActiveSupport::Notifications.publish can be used to publish anything, whether it's a standard Rails instrumentation payload, a string, or even a custom object, it's dangerous for the logger to accept anything that's being published.

So this PR filters out events that are not compatible with the default Rails instrumentation format to avoid issues.

closes #1131

Because `ActiveSupport::Notifications.publish` can be used to publish
anything, whether it's standard Rails instrumentation payload, a string,
or even a custom object, it's dangerous for the logger to accept anything
that's being published.

So this commit filters out events that are not compatible with the
default Rails instrumentation format to avoid issues.
@st0012 st0012 added this to the 4.0.1 milestone Dec 10, 2020
@st0012 st0012 self-assigned this Dec 10, 2020
@st0012 st0012 merged commit 1d7463d into master Dec 10, 2020
@st0012 st0012 deleted the fix-1131 branch December 10, 2020 16:42
@st0012
Copy link
Collaborator Author

st0012 commented Dec 11, 2020

fyi the fix has been released in 4.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sentry 4.0 incompatibility with ActiveSupport::Notifications.publish

2 participants