resque / resque/resque-scheduler
Updating to v4.2.0+ "loses" schedules
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.7k
- Forks
- 477
- PR merge metrics
- No merged PRs in 30d
Description
A recently-introduced change to the redis schema caused some unexpected behavior for at least one person when updating, as the schedules in redis appeared to have vanished. Manually renaming the key to match the new schema restored the schedules.
Preventing such surprises is a nice thing to do. I believe that adding something to the docs, change log, and maybe even adding a migration script would be nice, too. Thoughts? 💖
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
Start by reviewing pull request #535 and the Redis schedule key schema it introduced. Check the existing documentation and changelog guidance for upgrades, then determine whether a migration script is needed for old keys. Done means upgrades no longer make schedules appear missing, with the change and recovery path documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, ruby
- Domain
- backend, databases, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100