This repository has been archived by the owner on Jun 5, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here are a couple of fixes that we've used to be able to use Ruby to queue jobs and Python to run them. It's a great combo for us because the web guys like Ruby and the scientists like Python.
First fix: Ruby uses "::" to separate modules from classes, while python uses "."
so we'll sniff the queued class name for "::" and if it's there then
we're probably handling a job that was queued by Ruby.
Second fix: resque-web was crashing because pyres wrote the "run_at" field in a different format than resque. This fix makes pyres use the same format as resque so now resque-web can show pyres jobs.
Thanks!