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
Error in capturing low-level errors when using puma v4 #2067
Labels
Comments
Any news on this? I am facing the same error! |
@st0012 i'm a bit swamped rn, do you know why this would happen? |
same issue for me as well |
Upgrade to puma 5 helped. They don’t support puma 4.Best regards,Eugene Kovalev / Yevgeniy Kovalev / Eugeniusz KowalewOn 12 Oct 2023, at 01:51, Nadir Khan ***@***.***> wrote:
same issue for me as well
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
getsantry
bot
added
Waiting for: Community
and removed
Waiting for: Product Owner
labels
Oct 13, 2023
@sl0thentr0py Yeah it's because of the puma patch. I'll open a fix shortly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
I got an error in capturing low-level errors when using puma v4.
The following error messages are output in large numbers.
I think the related PR is below.
There seems to have been arguments change in the following PR that went into puma v5.
Reproduction Steps
Gemfile
Start server
bundle exec rails server
Expected Behavior
No error messages should be output.
Actual Behavior
Error message is output.
Ruby Version
3.1.4
SDK Version
5.10.0
Integration and Its Version
Puma 4.3.12
Sentry Config
No response
The text was updated successfully, but these errors were encountered: