Yep, your guess looks correct. We enforced creation of a public username
at registration a long while back, but it looks like the API doesn't do the
same enforcement (and neither does the web interface, anymore -- d'oh).
I'll get a bugfix out shortly.
On Thu, May 22, 2014 at 11:12 AM, Evan Bollig <boll0...@umn.edu> wrote:
> I have a fresh instance of galaxy-dist#stable. I create users and
> upload a workflow via the internal python api, and then I attempt to
> edit and download the workflow from the workflow editor tab. I click
> the direct download link and get the attached exception.
> I found that the exception is avoided if I instead share/export the
> workflow and then create a public username when prompted. When I go
> back and use the direct download link again, it works. Not sure if
> they're directly connected, but something in the share/export seems to
> band-aid the other. Presumably the 'None' should be the public
> -Evan Bollig
> Research Associate | Application Developer | User Support Consultant
> Minnesota Supercomputing Institute
> 599 Walter Library
> 612 624 1447
> 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:
> To search Galaxy mailing lists use the unified search at:
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:
To search Galaxy mailing lists use the unified search at: