[galaxy-dev] Error running workflow via API
The API interface is translating my parameters into python repr strings instead of actual strings. A command that should look like this: createPrimerFile.py /minilims/galaxy-data/primerTemplates/nextera.2x.primers.fasta NN NN /slipstream/galaxy/production/data/files/020/dataset_20664.dat is getting run as this: createPrimerFile.py /minilims/galaxy-data/primerTemplates/nextera.2x.primers.fasta __lt__galaxy.tools.parameters.basic.RuntimeValue object at 0x792be10__gt__ NN /slipstream/galaxy/production/data/files/020/dataset_20728.dat The input table in the tool info page is: Input Parameter Value Note for rerun chemistry type: galaxy.tools.parameters.basic.RuntimeValue object at 0x7fee4425ca10 First barcode NN Second (optional) barcode NN I’m running a slightly out of date version of Galaxy (I think it is change set 11080:87b586afb054) because this is BioTeam’s Slipstream appliance. Is there any chance this is a known bug? I didn’t see anything in Trello, but I’m really not sure I’ve got the hang of Trello yet. Thanks -john smime.p7s Description: S/MIME cryptographic signature ___ 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/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] Error running workflow via API
I’ve figured this one out. The tool id changed one me. Sorry for the spam. -j On Apr 9, 2014, at 4:48 PM, John Marmaduke Eppley jmepp...@mit.edu wrote: The API interface is translating my parameters into python repr strings instead of actual strings. A command that should look like this: createPrimerFile.py /minilims/galaxy-data/primerTemplates/nextera.2x.primers.fasta NN NN /slipstream/galaxy/production/data/files/020/dataset_20664.dat is getting run as this: createPrimerFile.py /minilims/galaxy-data/primerTemplates/nextera.2x.primers.fasta __lt__galaxy.tools.parameters.basic.RuntimeValue object at 0x792be10__gt__ NN /slipstream/galaxy/production/data/files/020/dataset_20728.dat The input table in the tool info page is: Input Parameter Value Note for rerun chemistry type: galaxy.tools.parameters.basic.RuntimeValue object at 0x7fee4425ca10 First barcode NN Second (optional) barcode NN I’m running a slightly out of date version of Galaxy (I think it is change set 11080:87b586afb054) because this is BioTeam’s Slipstream appliance. Is there any chance this is a known bug? I didn’t see anything in Trello, but I’m really not sure I’ve got the hang of Trello yet. Thanks -john ___ 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/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ smime.p7s Description: S/MIME cryptographic signature ___ 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/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
[galaxy-dev] Error running workflow via API
The API interface is translating my parameters into python repr strings instead of actual strings. A command that should look like this: createPrimerFile.py /minilims/galaxy-data/primerTemplates/nextera.2x.primers.fasta NN NN /slipstream/galaxy/production/data/files/020/dataset_20664.dat is getting run as this: createPrimerFile.py /minilims/galaxy-data/primerTemplates/nextera.2x.primers.fasta __lt__galaxy.tools.parameters.basic.RuntimeValue object at 0x792be10__gt__ NN /slipstream/galaxy/production/data/files/020/dataset_20728.dat The input table in the tool info page is: Input Parameter Value Note for rerun chemistry type: galaxy.tools.parameters.basic.RuntimeValue object at 0x7fee4425ca10 First barcode NN Second (optional) barcode NN I’m running a slightly out of date version of Galaxy (I think it is change set 11080:87b586afb054) because this is BioTeam’s Slipstream appliance. Is there any chance this is a known bug? I didn’t see anything in Trello, but I’m really not sure I’ve got the hang of Trello yet. Thanks -john___ 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/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
[galaxy-dev] error running workflow
Hi all, I have added some tools to my local install of Galaxy. To get to my final results I have to do a lot of steps. When I try to run every step separately it turns out to work out fine. But when I try to run all steps at once with a workflow I get the following error message. OperationalError: (OperationalError) database is locked u'UPDATE dataset SET update_time=?, state=? WHERE dataset.id = ?' ['2012-07-02 11:34:48.135419', 'queued', 529] I have noticed that the processes eat a lot of my computer resources. Other than that I have no clue what the problem could be. Any tips are appreciated. Kind regards, Jaap van der Heijden ___ 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/
Re: [galaxy-dev] error running workflow
Hi Jaap are you using 'SQLite', if so, I recommend to switch to 'PostgreSQL', see: http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Production%20Server/#Switching_to_a_database_server Regards, Hans On 07/02/2012 02:26 PM, j.w.f.van_der_heij...@lumc.nl wrote: Hi all, I have added some tools to my local install of Galaxy. To get to my final results I have to do a lot of steps. When I try to run every step separately it turns out to work out fine. But when I try to run all steps at once with a workflow I get the following error message. |OperationalError: (OperationalError) database is locked u'UPDATE dataset SET update_time=?, state=? WHERE dataset.id = ?' ['2012-07-02 11:34:48.135419', 'queued', 529] I have noticed that the processes eat a lot of my computer resources. Other than that I have no clue what the problem could be. Any tips are appreciated. Kind regards, Jaap van der Heijden | ___ 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/ ___ 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/
