Hi Carl,
Yes, the problem is fixed. Thank you very much. Just in
case, I see that galaxy-release-15.05 is now free of this
bug but galaxy-release-15.07 has this bug again.
Cheers,
Ata
On Wednesday 2015-07-15 07:54, Carl Eberhard wrote:
Date: Wed, 15 Jul 2015 07:54:05
From: Carl Eberhard
Hi Lionel
Sounds like Galaxy does not know what format your FASTQ file is. When you
click on it, what format does it show? Is it simple fastq? And how did you
get it into Galaxy?
You might need to manually specify the format by clicking on the Edit
Attributes button (the pencil icon) and select t
When running a Tophat job for over a hour, I get the following message and the
job stops.
Would anyone know why and is there a way to stop Galaxy from cleaning up the
job working
directory so that I can check the error log files?
Dwayne
galaxy.jobs.runners.local DEBUG 2015-07-14 16:54:10,478 ex
Hi,
Thanks for your answers. I understand that permit to load or create
"unsorted bam" (or sorted by name) can create bug with lot of tools
and it's difficult to restrict this manipulation just for few tools.
But I don't understand one thing. Why can I download from the toolshed
a tool which permi
On Jul 17, 2015 11:00 AM,
wrote:
> Send galaxy-dev mailing list submissions to
> galaxy-dev@lists.galaxyproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.galaxyproject.org/listinfo/galaxy-dev
> or, via email, send a message with subject or b
Hello,
I have a problem when I try to align en FATSQ file for a ChIP-seq.
I have done a FASTQ grooming because it has been performed on Illumina. No
my file is a .FASTSANGER.
However my file is not recognized. I see this : No fastqsanger,
fastqillumina or fastqsolexa dataset collection available.
It would be best practice to do this. Nate is working on packaging
(.deb) and our Anisble setup to accomplish this - getting these
permissions exactly correct I think will be a big part of that effort.
All of that said - if you were really going to pursue this but just
install and use the tool she
hi everybody
I'd like to ask if you think it's worthwhile is pursuing
finely grained tree permissions? Would this improve security
to leave out everything but only files/folders necessary for
writing - to galaxy user what needs to write everything else
root?
Or just full perms to galaxy user
So it appears the error we encountered was because we just collected the
pull requests that concern the max_metada fix and applied them to the
release_15.05 of galaxy cloned from mercurial.
To resolve our problems we had to switch to git and then to checkout
release 15.05.
The below steps worked f
