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
Log loaded extensions behind PUMA_DEBUG
#3020
Labels
Comments
JFYI, this week I did briefly look for the code that generated this; I couldn't find it. I'll look more this weekend, otherwise may rewrite. Regardless, anyone else can contribute. |
jeremyevans
added a commit
to jeremyevans/puma
that referenced
this issue
Dec 10, 2022
Not sure if this is the best place for it, but trying to move it to a separate method seemed challenging as this appears to be called for multiple places. Fixes puma#3020
jeremyevans
added a commit
to jeremyevans/puma
that referenced
this issue
Dec 10, 2022
Not sure if this is the best place for it, but trying to move it to a separate method seemed challenging as this appears to be called for multiple places. Closes puma#3020
7 tasks
MSP-Greg
pushed a commit
to jeremyevans/puma
that referenced
this issue
Dec 11, 2022
Not sure if this is the best place for it, but trying to move it to a separate method seemed challenging as this appears to be called for multiple places. Closes puma#3020
MSP-Greg
pushed a commit
to jeremyevans/puma
that referenced
this issue
Dec 13, 2022
Not sure if this is the best place for it, but trying to move it to a separate method seemed challenging as this appears to be called for multiple places. Closes puma#3020
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Re the 'loaded extensions', maybe something like the below?
Single mode:
Cluster mode:
EDIT: Above were generated without io-wait in Gemfile.lock
Originally posted by @MSP-Greg in #2843 (comment)
The text was updated successfully, but these errors were encountered: