Hi,
I run upgrade: hg pull -u -r 40f1816d6857 on our local instance, and I'm
now unable to start Galaxy..
Here is the content of Galaxy_log:
Traceback (most recent call last):
File galaxy_dir/galaxy-dist/lib/galaxy/web/buildapp.py, line 81,
in app_factory
from galaxy.app import
Hi,
We emailed previously about possible memory leaks in our installation of Galaxy
here on the HPC at Bristol. We can run Galaxy just fine on our login node but
when we integrate into the cluster using pbs job runner the whole thing falls
over - almost certainly due to a memory leak. In
Hi all,
Thanks Hans for giving a hint as to what we might need to try, we
tried pasing True and False for the is selected field and the Galaxy
form validation still doesn't like it, turns out it's the option value
fields that have to be stringified in your JSON encoder so that you
JSON reads:
On Mar 13, 2012, at 11:08 AM, Alban Lermine wrote:
Hi Alban,
Is your Galaxy server behind a firewall or without network access such that
it cannot access http://eggs.g2.bx.psu.edu/ ?
What happens if you run `python scripts/fetch_eggs.py` by hand?
Is there a way to downgrade Galaxy?
On Mar 13, 2012, at 6:59 AM, David Matthews wrote:
Hi,
We emailed previously about possible memory leaks in our installation of
Galaxy here on the HPC at Bristol. We can run Galaxy just fine on our login
node but when we integrate into the cluster using pbs job runner the whole
thing
Edward, I've marked your hmmscan repository as deleted so it will not longer be
displayed. I can undelete it if requested by anyone.
Peter, I've left your deprecated repositories alone, so they are still
accessible. I'll mark them deleted as well if you want.
On Mar 6, 2012, at 3:37 PM,
On Mar 13, 2012, at 10:36 AM, Alban Lermine wrote:
Hi,
I run upgrade: hg pull -u -r 40f1816d6857 on our local instance, and I'm
now unable to start Galaxy..
Here is the content of Galaxy_log:
Traceback (most recent call last):
File galaxy_dir/galaxy-dist/lib/galaxy/web/buildapp.py,
