Re: [galaxy-dev] failure to export workflows
Hi John and thanks for your feedback, yes, this affects all workflows of the instance though since it is our development instance there are not so many. I came to the posted output along the usual way I guess, i.e., from the workflow section I am choosing Download or Export for a workflow, which takes me, for example, to http://127.0.0.1:8080/workflow/export?id=f597429621d6eb2b, from where I click on Download workflow to file so that it can be saved or imported into another Galaxy server. and that's when it happens. Since you said that the username is missing from the link I thought this could be some login-related problem so I tried to log into different accounts and created new workflows there. They all have the same problem. Luckily, I checked and our production server is not affected although it runs the same release. So if you do not know how to fix this, I guess I will just set up a fresh development server and see whether that fixes it. Thanks, Wolfgang On 10/13/2014 02:34 AM, John Chilton wrote: I was unable to reproduce this problem. Can you supply more details - what path did you take through the UI to get that URL? Is that restricted to just some workflows or do all workflows have this problem as far as you can tell? I guess ultimately the reason that workflow isn't downloading is that it doesn't seem to have a user associated with it. The route should be /u/username/w/workflow_slug/json-download. /u/w/myworkflow/json-download doesn't appear to have a user name. Any clue how that happened? Do all newly created workflows have that same issue with your Galaxy instance? Sorry I have not been of more help. -John On Sun, Oct 12, 2014 at 10:50 AM, Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de wrote: Dear all, our local Galaxy does not seem to be able to export workflows anymore, instead fails with, for example: Not Found The resource could not be found. No route for /u/w/myworkflow/json-download We are running latest_2014.10.06 . Has anyone else experienced this ? Thanks, Wolfgang ___ 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/ ___ 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] failure to export workflows
Hi again, I figured it out !! It only works if the user has a Public Name. Once you choose one as an existing user, it works just fine with that name getting inserted into the link. Your feedback was really helpful, thanks a lot !! I am a bit confused though: I thought the Public Name was optional ? Is that not the case anymore ? Thanks again, Wolfgang On 10/13/2014 02:34 AM, John Chilton wrote: I was unable to reproduce this problem. Can you supply more details - what path did you take through the UI to get that URL? Is that restricted to just some workflows or do all workflows have this problem as far as you can tell? I guess ultimately the reason that workflow isn't downloading is that it doesn't seem to have a user associated with it. The route should be /u/username/w/workflow_slug/json-download. /u/w/myworkflow/json-download doesn't appear to have a user name. Any clue how that happened? Do all newly created workflows have that same issue with your Galaxy instance? Sorry I have not been of more help. -John On Sun, Oct 12, 2014 at 10:50 AM, Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de wrote: Dear all, our local Galaxy does not seem to be able to export workflows anymore, instead fails with, for example: Not Found The resource could not be found. No route for /u/w/myworkflow/json-download We are running latest_2014.10.06 . Has anyone else experienced this ? Thanks, Wolfgang ___ 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/ ___ 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] failure to export workflows
My understanding is that it was briefly optional (and maybe just through the API) but that was a bug. I think Dannon made that fix a few months ago. Sorry for the confusion. -John On Mon, Oct 13, 2014 at 4:44 AM, Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de wrote: Hi again, I figured it out !! It only works if the user has a Public Name. Once you choose one as an existing user, it works just fine with that name getting inserted into the link. Your feedback was really helpful, thanks a lot !! I am a bit confused though: I thought the Public Name was optional ? Is that not the case anymore ? Thanks again, Wolfgang On 10/13/2014 02:34 AM, John Chilton wrote: I was unable to reproduce this problem. Can you supply more details - what path did you take through the UI to get that URL? Is that restricted to just some workflows or do all workflows have this problem as far as you can tell? I guess ultimately the reason that workflow isn't downloading is that it doesn't seem to have a user associated with it. The route should be /u/username/w/workflow_slug/json-download. /u/w/myworkflow/json-download doesn't appear to have a user name. Any clue how that happened? Do all newly created workflows have that same issue with your Galaxy instance? Sorry I have not been of more help. -John On Sun, Oct 12, 2014 at 10:50 AM, Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de wrote: Dear all, our local Galaxy does not seem to be able to export workflows anymore, instead fails with, for example: Not Found The resource could not be found. No route for /u/w/myworkflow/json-download We are running latest_2014.10.06 . Has anyone else experienced this ? Thanks, Wolfgang ___ 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/ ___ 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] failure to export workflows
On Mon, Oct 13, 2014 at 8:14 AM, John Chilton jmchil...@gmail.com wrote: My understanding is that it was briefly optional (and maybe just through the API) but that was a bug. I think Dannon made that fix a few months ago. Sorry for the confusion. This is correct, public usernames are required and there was a bug that was incorrectly validating empty ones. ___ 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] failure to export workflows
On 13.10.2014 14:23, Dannon Baker wrote: On Mon, Oct 13, 2014 at 8:14 AM, John Chilton jmchil...@gmail.com mailto:jmchil...@gmail.com wrote: My understanding is that it was briefly optional (and maybe just through the API) but that was a bug. I think Dannon made that fix a few months ago. Sorry for the confusion. This is correct, public usernames are required and there was a bug that was incorrectly validating empty ones. Thanks for clarifying. I'll fix the affected accounts. Best, Wolfgang ___ 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] failure to export workflows
Dear all, our local Galaxy does not seem to be able to export workflows anymore, instead fails with, for example: Not Found The resource could not be found. No route for /u/w/myworkflow/json-download We are running latest_2014.10.06 . Has anyone else experienced this ? Thanks, Wolfgang ___ 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] failure to export workflows
I was unable to reproduce this problem. Can you supply more details - what path did you take through the UI to get that URL? Is that restricted to just some workflows or do all workflows have this problem as far as you can tell? I guess ultimately the reason that workflow isn't downloading is that it doesn't seem to have a user associated with it. The route should be /u/username/w/workflow_slug/json-download. /u/w/myworkflow/json-download doesn't appear to have a user name. Any clue how that happened? Do all newly created workflows have that same issue with your Galaxy instance? Sorry I have not been of more help. -John On Sun, Oct 12, 2014 at 10:50 AM, Wolfgang Maier wolfgang.ma...@biologie.uni-freiburg.de wrote: Dear all, our local Galaxy does not seem to be able to export workflows anymore, instead fails with, for example: Not Found The resource could not be found. No route for /u/w/myworkflow/json-download We are running latest_2014.10.06 . Has anyone else experienced this ? Thanks, Wolfgang ___ 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/ ___ 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/
