Hi,
when I use the example_watch_folder.py to check for files in an input
directory and process them if they are present. The workflow runs to completion
successfully, but the example_watch_folder.py task crashes with the following
errors, thus it can only process one file at a time, as the
Andrew,
Thanks for investigating this. I changed the subject and sent to the galaxy dev
list.
I've had a number of tools quit working recently. Particularly tools that
inspect the extra_files_path when setting metadata, Defuse, Rsem, SnpEff.
I think there was a change in the galaxy
Dear all,
I've installed a galaxy cloud cluster using usergalaxy.org/cloudlaunch
It runs fine, but I need to know how to let the cluster run on THCondor or
slurm instead of SGE. I can see that Condor is already installed on the
galaxy-master node since the condor_status command is there. But
When you say p.s. there is nothing in the log file.?
Does you mean the Galaxy log file? If there are jobs running and
completing there must be something in the log file right? Do you mean
there are just not tracebacks indicating errors in the logs?
My guess is the response is just taking a while
Changing the default job manager is not interchangeable in an automated
fashion. SGE is currently the main job manager that Galaxy has been
configured to be used with. Slurm will replace SGE in the next Galaxy
CloudMan release. HTCondor has been added as an experimental module but due
to the lack
When I click get output in the UCSC main table browser in firefox nothing
happens.
I can fix this by going to about:config in firefox and disabling
security.mixed_content.block_active_content
I am running galaxy behind an apache proxy using https as we have users
authenticate with their
Recently I tried to upload some annotation/reference files into Galaxy. After
couple failed tries using the upload method, I was able to do it via the using
the full file path. However, after these tries/retries, I believe Galaxy
database got confused and was corrupted. Existing workflows
Hello,
When starting Galaxy after updating it we get the assertion errors that
follow the following format:
galaxy.datatypes.registry ERROR 2014-10-14 15:51:40,004 Error loading
display application (./display_applications/ucsc/bam.xml): Filename and id
attributes required for dynamic_links
Hello all,
Well, the results are unanimous: Keep it; it's worth the time invested
Where to put it was far from unanimous, so we'll experiment with putting it
in both the monthly newsletter and dev news briefs.
Thanks all,
Dave C.
On Wed, Oct 8, 2014 at 9:42 AM, Dave Clements
