Hi Dave et al,
Yesterday I uploaded a new tool to the TestToolShed:
http://testtoolshed.g2.bx.psu.edu/view/peterjc/blast_rbh
Development repository:
https://github.com/peterjc/galaxy_blast/tree/master/tools/blast_rbh
It is currently listed under Latest revision: failing tool tests,
Name Latest
Hi Peter,
I doscovered an error in the query filters that are used for rendering these
various Latest revision: lists. The problem was that the filters were not
correctly determining whether the revisions had been tested yet by the install
and test framework. This problem should be fixed in
Great - thanks Greg,
Peter
On Fri, May 16, 2014 at 2:59 PM, Greg Von Kuster g...@bx.psu.edu wrote:
Hi Peter,
I doscovered an error in the query filters that are used for rendering these
various Latest revision: lists. The problem was that the filters were not
correctly determining
Hi All,
I have been trying to get the visualization through ucsc main working, thus
I installed the nginx on our ubuntu(the one comes with update), then I
configured it according to the wiki
https://wiki.galaxyproject.org/Admin/Config/nginxProxy
Here is the section in my nginx.conf
I have an empty posgresql database:
psql -c create database galaxy;
I'm trying to launch run.sh from the latest version of galaxy-dist.
Migration proceeds normally up to this point:
#
galaxy.model.migrate.check INFO 2014-05-16 19:11:17,121
galaxy.model.migrate.check INFO 2014-05-16
On Fri, May 16, 2014 at 3:33 PM, Evan Bollig boll0...@umn.edu wrote:
InvalidVersionError: 103 is not 105
This would indicate to me that migration script 104 failed.
My question is: why can't the manage_db.sh upgrade step be included
automatically when the initial DB build fails?
It is, in
