-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[20.09] Fix mule job messaging #11148
[20.09] Fix mule job messaging #11148
Conversation
Ah, I tried updating my Galaxy from 19.01 to 20.09 and all works but jobs stuck in "new" state... we use Mule handlers too so hopefully pulling this will fix it. thanks |
@nsoranzo the circle-ci setup breaks when changing the base. Let me see if a rebase fixes that |
would be good to have this fix. thanks! |
Handler assignment via mule messaging passes arpund the job id, so we need to flush before we can assign. Should fix galaxyproject#11146.
da7556a
to
152d3b4
Compare
awaiting this to be merged. would be great to have Mule job messaging and job submission resolved |
Thanks both. I contacted @nsoranzo who suggested pulling this fix #11148 (pulled this commit only which has 2 files changed) but same issues persist. I also noticed in .logs that also get: Not sure how to proceed as my galaxy.yml, job_conf.xml etc look good and have restarted galaxy since pulling the fix too but my test jobs (very |
e.g., on launching a test job:
but handler logs empty and jobs_directory has no new dir. |
@AjitPS please open an issue and describe your setup, including python version used and your job handler setup. The message your seeing here means the PR works. |
Handler assignment via mule messaging passes around the job id, so we need to flush before we can assign.
Should fix #11146.