Skip to content
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.

a couple of Ruby-compatibility fixes #146

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

caboteria
Copy link
Contributor

@caboteria caboteria commented Feb 6, 2016

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!

toby cabot added 2 commits July 1, 2015 18:22
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.
Resque expects that the run_at value will be an ISO8601 string in UTC.
Pyres was writing seconds since the epoch, which caused resque-web to
crash.
@caboteria caboteria changed the title handle ruby-style Module::Class names a couple of Ruby-compatibility fixes Nov 18, 2016
@caboteria
Copy link
Contributor Author

Hi, I added a second commit to this branch a few days ago. It makes pyres compatible with the resque-web UI. Previously it wrote the run_at timestamp in a format that made resque-web crash but 65c3e34 changes the format so it's similar to the Ruby resque format and now the UI works.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant