-
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
4.3.0 fails to load config that works in 4.2.0 #136
Comments
This seems to be a redis_store_proxy issue. This line passes 'raw: true' param to redis get method, but redis get method only accepts one argument: 'key'. Hence the (wrong number of arguments (2 for 1)) error. |
Seems reasonable, but any idea why it works in Rack Attack 4.2? (the only change required to my gemfile was specifying rack-attack 4.2.0 in my Gemfile for it to work again). |
Erm, I responded with the misunderstanding redis_store_proxy was an external thing which had not changed. (I was confusing it with redis-namespace). I would delete the previous comment but you probably already got notifications. Anyway thanks for finding the issue, I'll watch this thread to see what happens next :) |
… possible to implement something like: ```store.write(key, 0, :expires_in => expires_in)``` See #113
@trinode, on the second thought, you might be passing the wrong object to the It should probably be one of the following: I.e. |
I recently cleaned up some of the cache store code in v4.4.1 (see #165). I think it'll fix this case too (though I haven't been able to recreate). Please try upgrading again, and re-open this if the problem persists. |
Update: forcing a downgrade to 4.2.0 from 4.3.0 solved the issue, no other changes. so this appears to be the latest version that doesn't work
The file below is no longer working, I'm getting the error
ArgumentError (wrong number of arguments (2 for 1)):
config/initializers/rack_attack.rb:22:in `block in class:Attack'
(The line is the first Rack::Attack::Allow2Ban call)
I think it's a new version of rack that's the issue, but I could be wrong so:-
Here's my gemfile.lock if it helps:-
The text was updated successfully, but these errors were encountered: