Allow setting redis options - #132
Conversation
|
I tried running the specs, but got: 🤔 |
|
@krzyzak 👀 |
I think it's because of ruby-concurrency/concurrent-ruby@d7ce956 |
|
Weirdly enough this PR has no github actions to run 🤔 |
|
Hey folks, I want to use Gush on our project, but we face this issue of not having options for Redis, as say, Sidekiq has. I've looked in to the issue with specs, and managed to resolve it, by changing rails_version in the Gemfile: This allows |
|
thanks @nplusp I updated the Gemfile as you suggested. lets see if that triggers github actions now |
ah, the tests run now, but most of them fail with |
|
@wnm interesting - I cannot reproduce that issue within you branch. Do you run rspec with prepending |
|
@nplusp yes, it also shows the failing tests in the workflows now: https://github.com/wnm/gush/actions/runs/20033903532 |
|
Oh yes, another fix would be either to add |
|
I also have noticed a few specs that were failing locally, adding these to reset cached configuration helped: |
The new redis-options spec sets config.redis = { db: 1 }, but the
before(:each) hook only reset redis_url, leaving the redis hash to leak
into later tests. Reset the whole redis hash each example instead.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
@krzyzak fixed tests locally, can you approve the pending workflow here? |
No description provided.