On Fri, Jan 10, 2014 at 3:45 AM, neil.burd...@csiro.au wrote:
Hi,
I have a tool that works well. However, when I download the results, the
results are zipped up but included into the zip file is the *.html file
(with the same name as the tool output) do you know how I can stop this from
The changes you're looking at are in galaxy-central, and I'm assuming your
local codebase is tracking galaxy-dist, our release repository. You can
wait for these changes to propagate through our release process over to
galaxy-dist (I think this is scheduled to happen in early February), or, if
I am stumped, I am not sure how this would happen. How did you apply
the patch against the -dist stable code? Can you send me the full
contents of the patched ..api/library_contents.py file?
-John
On Tue, Jan 7, 2014 at 9:48 AM, Olivia Doppelt
olivia.dopp...@pasteur.fr wrote:
Dear John,
Hello Andrea,
Are you still having login issues?
The first thing to double check is that you confirmed your registration.
Did you get an email with a link? I am wondering because the address you
have below differs in capitalization from the address you are sending
from, and your Galaxy
I've seen
$__app__.tool_data_tables[ 'all_fasta' ].get_fields() )[0][-1]
in tool xml templates. Is there a way I can access the tool_data_tables
structure from python code too?
I see all the initialization stuff happening in
Just to clarify do you want to access them from Galaxy web server code
or from a Galaxy tool wrapper written in Python?
Nearly every part of the Galaxy source code has access to app and
everything inside of it, for instance all controller methods take in a
trans variable that contains a reference
