Skip to content
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

Use recommended sentry send mechanism #1150

Conversation

senid231
Copy link
Member

@senid231 senid231 commented Jun 27, 2022

In order to prevent deserialization error and extra memory consumption by sentry errors sending

See getsentry/sentry-ruby#1522
and https://docs.sentry.io/platforms/ruby/configuration/options/#optional-settings

In order to prevent deserialization error and extra memory consumption by sentry errors sending
@senid231 senid231 self-assigned this Jun 27, 2022
@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 83.549% when pulling b81e213 on senid231:fix-deserialization-error-during-send-sentry-event into b6fdcc8 on yeti-switch:master.

@Fivell Fivell merged commit 98fe34f into yeti-switch:master Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants