Hi Frank,
This should be resolved as of changeset 7057:08fbfeaaf3e1. Thanks!
-Dannon
On Mar 27, 2012, at 4:37 AM, Frank Sørensen wrote:
Hi Dannon,
Unfortunately our server is (still) behind a firewall, so I can't share
anything, but I hope you can reproduce the error from the following
Thanks.
I have set up Mercurial to fetch updates from galaxy-dist, and it seems
that my version of galaxy is up to date.
- Should I pull from galaxy-central to get this update (7057:08fbfeaaf3e1)?
- If so, could you please tell me how I do that?
- Do you know how I permanently change
On Apr 18, 2012, at 8:44 AM, Frank Sørensen wrote:
- Should I pull from galaxy-central to get this update (7057:08fbfeaaf3e1)?
- If so, could you please tell me how I do that?
Sure, you can pull from galaxy-central by issuing a manual pull with source
from your galaxy-dist directory:
hg
Hi Dannon,
Unfortunately our server is (still) behind a firewall, so I can't share
anything, but I hope you can reproduce the error from the following
description.
If I make a vanilla test workflow say:
Input Dataset - Map with BWA for Illumina (single end) - SAM-to-BAM -
flagstat
and
Hi,
I seem to have some problems with the visibility of tool outputs in my
workflows. When I flag any given output as visible, Galaxy sometimes
decides to hide it in the resulting history anyway. I can't find any
systematic behavior though. It seems to be rather arbitrary weather
Galaxy
Could you share an offending workflow with me? Or is it any workflow? I've
not seen this behavior before, but it definitely shouldn't be random. So in
your situation the same workflow run multiple times will not consistently hide
the same datasets?
-Dannon
On Mar 23, 2012, at 6:05 AM,
