0.4.0 seems to break REDIS_HOST env variable
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 456
- Forks
- 149
- Avg merge
- 9d 7h
- Merged PRs (30d)
- 3
Description
I updated our resque pool gem from 0.3.0 to 0.4.0 and had to roll back because what had previously worked for passing the redis host variable to resque-pool no longer does.
I use god to manage resque, so I have a watch that passes the REDIS_HOST via the watch.env variable, but after the upgrade resque-pool changed from using my configured host location to localhost. Since this crashed the whole system on startup I can't comment on whether any other environment variables are getting through any better.
I've rolled back to 0.3.0 for now.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the regression with resque-pool 0.4.0, Redis, and god's watch.env setting for REDIS_HOST, comparing it with 0.3.0. No source file or test is named in the issue; done means the configured Redis host is passed through and resque-pool starts successfully instead of falling back to localhost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100