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
Accept sentinel options even with string keys #599
Conversation
+1 |
Travis specs fail on Ruby
This is not related to the code changes though. Tests pass locally, but I would love to see the build pass on different Ruby versions on Travis. Could this be an issue with the version of |
More the fact that we don't restrict the rake version and therefore the latest one is pulled which is now incompatible with Ruby 1.8.7 We will pull the plug on 1.8.7 eventually. |
I see ;) |
It is possible to fix this by adding, in the gemspec, something like this: if RUBY_VERSION == "1.8.7"
s.add_development_dependency "rake", "~> 10.0"
else
s.add_development_dependency "rake"
end That would make the build run. Should I do that as part of this PR, or separately, or skip it completely? |
I don't like the conditional there. We don't depend on any newer features, so we can stick with 10.0 for all Ruby versions for now (this is only a development dependency and should not cause trouble to other gems) |
OK, tests are passing now. I also had to make sure a recent version of bundler is used for CI, to fix failures on jRuby head. And close/reopen PR to force Travis to rebuild. |
just helped someone who got burned by this issue - seems like the concerns about rake version mentioned above should be addressed now, since #601 is now in master. Would this PR be ready to merge if we remove the parts that deal with the rake version? Happy to submit a modified PR myself if that helps. |
Any chance we can get this PR finished off and approved? |
As far as I know, this is finished (tests were passing), although I sent it 4 years ago so things might have changed? |
37220f0
to
3b77b39
Compare
Before, the sentinel options were assumed to have symbol keys, so string keys were ignored. This is surprising, as other Redis options can be indifferently passed as symbols or strings. Now string keys are allowed too.
3b77b39
to
c452de8
Compare
I took care of rebasing on the current master, fixing the conflicts, and adapting this PR to the things that have changed since it was open 4 years ago. The part dealing with the Rake version is obsolete and was removed. Some context on the changes: the |
Awesome! Can we get a member of the Redis team to review? cc: @byroot |
Before, the sentinel options were assumed to have symbol keys, so string keys
were ignored. This is surprising, as other Redis options can be indifferently
passed as symbols or strings. Now string keys are allowed too.