-
Notifications
You must be signed in to change notification settings - Fork 337
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
NameError uninitialized constant using threaded server #229
Comments
Any resolution on this? We're getting this periodically as well. Same situation as above with the following versions: |
Hi there, Created test rails app with:
And tested with 10K (10 concurrent) requests using Apache Bench and wasn't able to reproduce the exception. Here is the test app https://github.com/grzuy/rails_test_app_for_rack_attack_229, feel free to try make the error appear by adding any more configuration similar to what you have in yours :-) |
@dhartoto If you have a stack trace of the exception, that would be helpful also :-) |
Thanks @grzuy. This doesn't happen very often it only pops up once in awhile.
I'll have a play with your test app later today :) |
@dhartoto Thanks. Are you adding anything to rails |
@dhartoto Hi, i am still trying to reproduce this issue. Maybe your Thanks again. |
@grzuy so sorry for my late reply. Been caught up. Here's my puma config:
And my Procfile:
|
No, Heroku shouldn't be a problem at all. I am just gathering info about you setup to see if that helps me, either reproduce the issue on my end and/or help me understand what could be happening. Thanks! |
@dhartoto A couple of questions.
|
@grzuy, the answer is no to both your questions. |
we are getting the same issue |
@leofrozenyogurt could you also post your stack trace? Maybe we can converge to a common dependency between both of you. |
|
The stack traces are very similar. Here are the intersections: NewRelic RPM 4.3.0.335
Warden 1.2.7
Rack Timeout 0.4.2
Rack Deflater I'll see if I'm able to set up a testing app later tonight. Maybe you can use these gems in your test-app, @grzuy? |
I've tested with NewRelic and Rack Timeout with no success. I'm yet to set up Warden since it might take more time. @leofrozenyogurt @dhartoto are you using some kind of Authentication lib that makes use of Warden, such as Devise? |
We're also seeing the issue with Here's our stack trace:
|
@grzuy |
Hi @lmansur, the goal is is to have a new release sometime next week, if not before :-) |
@lmansur FWIW |
@jeffjo @dhartoto @NuckChorris @leofrozenyogurt Please report back if you are also able to reproduce Thanks! |
Closing for now. |
We are running:
rack-attack 4.2.0
rails 4.2.5.1
MRI ruby 2.3.1
puma 3.8.2
We are sometimes seeing
NameError uninitialized constant Rack::Attack::Request
when threading is enabled in Puma. I suspect this has something to do with the fact that rack-attack is usingautoload
. I came across this GH issue which describes what we're seeing. I was wondering if anyone else has encountered this kind of issue when running a multi-threaded web server.The text was updated successfully, but these errors were encountered: