History will not refresh after workflow submission via the API
Hi devs! After updating my local instance to changeset 19cbbaf566216cb46ecc6a6d17e0f1e0ab52978e my tool which submits a workflow via the API and set force_history_refresh to TRUE does not refresh the history anymore. The job is submit via DRMAA to SGE. Unfortunately the job seems to run forever because it is still in yellow state (even after SGE tells Galaxy that the job has finished. As soon as I refresh the history manually the according history entries get green and all entries for the submitted workflow are shown. I have no idea where I can have a look at. If you need any further information let me know! Thanks for your help in advance! Cheers, Sascha
Hi Sascha, This may be due to the recent history panel changes. Can you update to the latest revision and see if the error still occurs? Thanks, Carl On Tue, Nov 20, 2012 at 2:22 AM, MSc. Sascha Kastens < s.kastens@gatc-biotech.com> wrote:
Hi devs!
After updating my local instance to changeset 19cbbaf566216cb46ecc6a6d17e0f1e0ab52978e my tool which submits a workflow via the
API and set force_history_refresh to TRUE does not refresh the history anymore.
The job is submit via DRMAA to SGE. Unfortunately the job seems to run forever because it is still in yellow state (even after SGE tells Galaxy that the job has finished. As soon as I refresh the history manually the according history entries get green and all entries for the submitted workflow are shown.
I have no idea where I can have a look at. If you need any further information let me know!
Thanks for your help in advance!
Cheers,
Sascha
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
Hi Carl, I have updated to the latest revison but the error still occurs. Cheers, Sascha Original Message processed by CONSOLIDATE Subject: Re: [galaxy-dev] History will not refresh after workflow submission via the API Sent: Mittwoch, 21. November 2012 17:54 From: Carl Eberhard (carlfeberhard@gmail.com) Hi Sascha, This may be due to the recent history panel changes. Can you update to the latest revision and see if the error still occurs? Thanks, Carl On Tue, Nov 20, 2012 at 2:22 AM, MSc. Sascha Kastens <s.kastens@gatc-biotech.com> wrote: Hi devs! After updating my local instance to changeset 19cbbaf566216cb46ecc6a6d17e0f1e0ab52978e my tool which submits a workflow via the API and set force_history_refresh to TRUE does not refresh the history anymore. The job is submit via DRMAA to SGE. Unfortunately the job seems to run forever because it is still in yellow state (even after SGE tells Galaxy that the job has finished. As soon as I refresh the history manually the according history entries get green and all entries for the submitted workflow are shown. I have no idea where I can have a look at. If you need any further information let me know! Thanks for your help in advance! Cheers, Sascha ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
participants (2)
-
Carl Eberhard -
MSc. Sascha Kastens