Repost: Mike, please reply to the list threaded question to help us
track and to permit the entire Galaxy community to learn and contribute
to Q/A. Thanks!
-
Thanks for the response Jen!
Answers to your questions below.
1. It should be the newest version of Galaxy
2. We did make product
Thanks for the response Jen!
Answers to your questions below.
1. It should be the newest version of Galaxy
2. We did make production server changes but I'll check the admin part again
3. This might be the problem. I tried to install package_samtools_0_1_19
but it failed, then I insta
Hi Mike,
I am moving this over to the galaxy-...@bx.psu.edu mailing list as it
concerns a local install. This is the best way to make contact with
others working with the same type of Galaxy.
https://wiki.galaxyproject.org/MailingLists
A few things to provide more context that will help with
Hello Peter,
I've corrected this one as well - no tool test results should now be displayed
for the venn_list repository. Regarding roy, the test run that displayed that
result was Nov 30, which is quite a while back and may have been due to an
issue that has since been corrected. I believe r
Hi Neil,
You'll want to look at the users API controller, specifically the api_key
method. Your downstream tool could, upon receiving an empty API key from
the wrapper, generate a new key and use it (after which it'd also be
available to the user).
On Thu, Dec 5, 2013 at 9:05 PM, wrote:
> Hi
On Tue, Dec 10, 2013 at 2:46 PM, Greg Von Kuster wrote:
> Hello Peter,
>
> There are several "flags" for each repository revision that determine if and
> how
> the revision is tested. If tested, flags also detemine which category the
> latest
> revision falls into when clicking on the links in
Hello Nicola,
The main tool shed is running a bit behind the test tool shed since it is on
the stable branch. I've commited a fix for the main tool shed in
11664:3bf805dfa14e that should correct the problem resulting in no test results
being displayed. Results should begin being displayed wit
Hi Greg!
I don't know if it's the same problem, but I've not been able to see
test results for this repository for a while:
http://toolshed.g2.bx.psu.edu/view/crs4/blat
Best,
Nicola
Il giorno mar, 10/12/2013 alle 09.46 -0500, Greg Von Kuster ha scritto:
> There are several "flags" for each repo
Hello Peter,
There are several "flags" for each repository revision that determine if and
how the revision is tested. If tested, flags also detemine which category the
latest revision falls into when clicking on the links in the Tool Shed's menu.
One of these flags is "tools_functionally_corr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Galaxy developers,
I would be particularly interested in seeing this implemented as flow
control blocks. Having such blocks in workflows would vastly expand the
capabilities. Ideally there would be something like
- - for (i=0 to max)
- - foreach (fil
By creating sand-boxed Python using virtualenv, "sh run.sh"
runs fine.
On Tue, 10 Dec 2013, zong-pei@imm.ox.ac.uk wrote:
Date: Tue, 10 Dec 2013 10:01:56
From: zong-pei@imm.ox.ac.uk
To: galaxy-dev@lists.bx.psu.edu
Subject: [galaxy-dev] The latest galaxy-dist run.sh failed
Hi,
We've just
Dear galaxy-dev's,
about a year ago you discussed on variable number of inputs into a workflow
(see http://lists.bx.psu.edu/pipermail/galaxy-dev/2012-November/012012.html and
http://thread.gmane.org/gmane.science.biology.galaxy.devel/4502/focus=4502, for
example). We're interested in having som
Hi,
We've just installed the latest galaxy-dist:
hg clone https://bitbucket.org/galaxy/galaxy-dist/
cd galaxy-dist
hg -v update stable
The server runs: CentOS release 6.5, python 2.6.8, and
mysql-5.1.71-1.el6.x86_64
"sh run.sh" has failed:
..
migrate.versioning.repository DEBUG 2013-12-10
13 matches
Mail list logo
