Hi,
In the server logs I've found:
web0.log: galaxy.webapps.galaxy.api.histories ERROR 2013-01-11
19:56:21,071 Error in history API at showing history detail: History is
not accessible to the current user
web1.log: galaxy.webapps.galaxy.api.histories ERROR 2013-01-11
19:55:14,341 Error in
I saw this same problem with our upload1 set to run on the cluster (it had
worked properly a few months prior). I found out that the cluster sysadmins
had set the nodes for local access only (no web access), direct file uploads
and FTP to local disk worked but URL-based uploads did not.
The
Hi,
Has the devteam a schedule of the order of the tools they plan to
migrate to the tool shed?
Thanks,
Joachim.
--
Joachim Jacob
Rijvisschestraat 120, 9052 Zwijnaarde
Tel: +32 9 244.66.34
Bioinformatics Training and Services (BITS)
http://www.bits.vib.be
@bitsatvib
On Thursday, January 17, 2013, Carl Eberhard wrote:
Hello, Peter
The blank panel should definitely be handled more gracefully in this
situation - I'll work on that.
Great :)
Have you noticed though, since your patch, any particular pattern to which
metadata names are turning out to
I have a very basic STAR wrapper that works:
https://bitbucket.org/jgoecks/jeremys-code/src/fa1930a689b8e2f6b59cc1706e5ba0ed8ad357be/galaxy/tool-wrappers/star.xml?at=default
For now, the wrapper does two things: maps RNA-seq reads and identifies
chimeric reads/junctions. There are tons of
ProgrammingError: (ProgrammingError) You must not use 8-bit
bytestrings unless you use a text_factory that can interpret 8-bit
bytestrings (like text_factory = str). It is highly recommended that
you instead just switch your application to Unicode strings. u'UPDATE
job SET update_time=?, state=?,
ProgrammingError: (ProgrammingError) You must not use 8-bit
bytestrings unless you use a text_factory that can interpret 8-bit
bytestrings (like text_factory = str). It is highly recommended that
you instead just switch your application to Unicode strings. u'UPDATE
job SET update_time=?, state=?,
Hi guys,
We have updated our galaxy to 20 Dec 2012 release. Recently we found that
some submitted jobs could not start (stay gray forever).
We found that it was caused by the job manager sent jobs to a handler
(handler0) whose python process crashed and died.
From the handler log we found the
