Hi Dannon, A 'hg pull -u' brought me up to changeset 14925:2db0fb9594d6 so I'll
try later this week.I will tell you if everything went well.
Thanks,Cristian
Date: Tue, 9 Dec 2014 16:30:10 -0500
Subject: Re: [galaxy-dev] Manage jobs interface error
From: dannon.ba...@gmail.com
To: tuto...@hotmail.
Dear all,
I'm currently testing a software package we developed for installation
from the testtoolshed. Things seem to work fine mostly, but there is one
thing I don't know how to solve (if it can be solved).
Our package consists of 14 individual tools, which I uploaded as 14
separate reposi
Hi Wolfgang,
You didn't include the name or a link to your Test Tool Shed packages.
Are you talking about the suite_config.xml file?
I'm not sure if Galaxy still uses that, no-one answered my earlier question:
http://dev.list.galaxyproject.org/Role-of-suite-config-xml-in-current-Tool-Shed-tc46658
Hi all,
The "Repository dependency definitions" link is working on the
Main Tool Shed, but fails with the following exception on the
Test Tool Shed:
URL: http://testtoolshed.g2.bx.psu.edu/repository/browse_repository_dependencies
File
'/var/opt/galaxy/toolshed_data/test_toolshed/lib/galaxy/web/f
Hi Peter,
here's the link to the package:
https://testtoolshed.g2.bx.psu.edu/view/wolma/suite_mimodd_0_1_5
It is not using a suite_config.xml file (which I hear of for the first
time), but contains just a single repository_dependencies.xml file with
this content:
name="package_mimodd
On Thu, Nov 27, 2014 at 1:58 PM, Peter Cock wrote:
> Hi Guys,
>
> I retitled this since the TestToolShed does seem to be running tests
> regularly again. However, I still have a fair number failing with the
> cryptic status "Exception: History in error state."
>
> I guess the logging changes John
Thanks Wolfgang,
I think the suite_config.xml file was originally designed a subset of
the tool_conf.xml file, inserted into it at run time. I think it could hold
the tools in the desired order - probably with subsections and
labels too.
However, I suspect this may not be used with the current
To
On Wed, Dec 10, 2014 at 5:46 AM, Peter Cock wrote:
> On Thu, Nov 27, 2014 at 1:58 PM, Peter Cock wrote:
>> Hi Guys,
>>
>> I retitled this since the TestToolShed does seem to be running tests
>> regularly again. However, I still have a fair number failing with the
>> cryptic status "Exception: His
Peter -
When you have previously asked about suite_config.xml I grepped
around and I couldn't find any references to it, did some more greps
just now and I still cannot. My best guess is that is not being used
at all - but I am not a tool shed expert.
Wolfgang -
I am not aware of being able
On Wed, Dec 10, 2014 at 2:03 PM, John Chilton wrote:
> On Wed, Dec 10, 2014 at 5:46 AM, Peter Cock wrote:
>> Hi guys,
>>
>> The good news is my list of failing tools has shrunk to the following,
>> none of which seem to have been tested yet in December, stuck
>> with "Exception: Job in error stat
On Wed, Dec 10, 2014 at 2:08 PM, John Chilton wrote:
> Peter -
>
> When you have previously asked about suite_config.xml I grepped
> around and I couldn't find any references to it, did some more greps
> just now and I still cannot. My best guess is that is not being used
> at all - but I am not
Sorry for the late response to this. Under installation Status, it just
says "Error". There is no actual error message shown or link available.
There is a "?" next to the name. The description below the tools says
"Unable to get information from the Tool shed". I checked paster.log, but
don't s
On 10.12.2014 15:08, John Chilton wrote:
I am not aware of being able to enforce an ordering of these things.
It would be a nice feature obviously so I have created a Trello card
for the request - https://trello.com/c/lPOkD4BD.
Too bad this isn't possible yet, but thanks for adding the car
Hello. I am trying to configure our local production Galaxy server to
always use HTTPS on nginx. When I visit http://localhost I see the
main galaxy webpage where I can sign in. However, when I enter my
administrator credentials and click Login, the page tries to redirect
to HTTPS but then displays
Your nginx server doesn't seem to be listening on the HTTPS port, you need
this in the server config:
listen 443 default ssl;
Here's the relevant part of the Galaxy setup I have over here:
upstream galaxy_app {
server localhost:8080;
}
# redirect http to https
server
15 matches
Mail list logo
