-
-
Notifications
You must be signed in to change notification settings - Fork 178
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected message arrived into Sentry.Transport.Sender when using Finch #732
Labels
Comments
Interesting, yeah this is not supposed to happen. The Logger backend and handler use the same code to send exceptions (passing I wouldn't exclude that this might be an issue with Finch leaking messages, or nimble_pool (the pooling library that Finch uses) leaking messages. Should we try to open an issue in those too? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃憢
Environment
Sentry client version is 10.2.0, here's how it's configured:
Steps to Reproduce
I don't have steps to reproduce right now, but here's what happened:
The message looks similar to https://github.com/sneako/finch/blob/71f469c46d3d8ea9993d986789cef8d14bcc819c/lib/finch/http1/pool.ex#L201, but why did it arrive in Sentry.Transport.Sender is unclear: Sentry.Transport.Sender is supposed to be used only with logger handlers, and we use a custom logger backend still.
Expected Result
The goal of opening this issue is to find out what sent the message and why it was sent to Sentry.Transport.Sender.
The text was updated successfully, but these errors were encountered: