Hi Nate,

sorry to bother you again, but that issue is still not fixed for me.

The following is supposed to work, or?
<tool id="toolshed.g2.bx.psu.edu/repos/devteam/ncbi_blast_plus/ncbi_blastn_wrapper/" destination="24_cores_24G" /> <tool id="toolshed.g2.bx.psu.edu/repos/devteam/ncbi_blast_plus/ncbi_blastx_wrapper/" destination="24_cores_24G" /> <tool id="toolshed.g2.bx.psu.edu/repos/devteam/ncbi_blast_plus/ncbi_tblastn_wrapper/" destination="24_cores_24G" />
        <tool id="ncbi_blastp_wrapper" destination="24_cores_24G" />
<tool id="toolshed.g2.bx.psu.edu/repos/devteam/ncbi_blast_plus/ncbi_rpsblast_wrapper/" destination="24_cores_24G" /> <tool id="toolshed.g2.bx.psu.edu/repos/devteam/ncbi_blast_plus/ncbi_tblastx_wrapper/" destination="24_cores_24G" /> <tool id="toolshed.g2.bx.psu.edu/repos/peterjc/blast2go/blast2go/0.0.6" destination="20G_memory"/>


Thanks,
Bjoern


Am 14.02.2014 16:37, schrieb Nate Coraor:
Hi Björn,

It should be fixed, the problem was with tools with uppercase characters in
the guid:

     https://bitbucket.org/galaxy/galaxy-central/commits/0b955e54451c/

--nate


On Thu, Feb 13, 2014 at 2:38 AM, Björn Grüning <bjoern.gruen...@gmail.com>wrote:

Hi Nate & Simon,

was that solved? I think it's still not working? Or is that a
regression. In particular shed_host/repos/owner/repo/tool_id is not
working, and that is what is 90% needed, or?

Thanks,
Bjoern

From: Nate Coraor [mailto:n...@bx.psu.edu]

This should work, it looks like there may be a bug with handling tool
shed
IDs when determining job destinations. You are actually supposed to be
able to use any of:

   shed_host/repos/owner/repo/tool_id/version
   shed_host/repos/owner/repo/tool_id
   tool_id

I'll take a look at this as soon as possible.  One thing you might try
in
the short term is using the percent encoded tool id in the <tool> tag
in
job_conf.xml:

Hi Nate,

Using the percent encoded form was the first thing I tried (before
emailing the list).  It didn't make any difference.  I think there's
another reason it's not picking it up.  Thanks for looking into this.

cheers,
Simon


=======================================================================
Attention: The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the
sender immediately.
=======================================================================

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
   http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
   http://galaxyproject.org/search/mailinglists/




___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
 http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
 http://galaxyproject.org/search/mailinglists/

Reply via email to