Hello imon,
You are correct - this feature is not yet available on the main tool shed.
I'll add some code to handle this issue in a better way. However, the fact
that the main tool shed is not currently handles in a better way doesn't really
cause any problems in this case. So if you wanted to run the development
branch, the current behavior for this feature should not keep you from doing so.
Thanks for reporting this.
Greg Von Kuster
On Oct 13, 2013, at 5:13 PM, Simon Guest wrote:
> Hi Greg,
>
> I think this would be yours. I've recently upgraded to the
> development branch, and I'm getting HTTP 404 errors from the new
> function get_tool_shed_status_for_installed_repository().
>
> What gets logged is this:
> tool_shed.util.shed_util_common ERROR 2013-10-14 09:44:17,448 Error
> attempting to get tool shed status for installed repository emboss_datatypes:
> HTTP Error 404: Not Found
> Traceback (most recent call last):
> File "/home/galaxy-dev/galaxy/lib/tool_shed/util/shed_util_common.py", line
> 1226, in get_tool_shed_status_for_installed_repository
> encoded_tool_shed_status_dict = common_util.tool_shed_get( app,
> tool_shed_url, url )
> File "/home/galaxy-dev/galaxy/lib/tool_shed/util/common_util.py", line 191,
> in tool_shed_get
> response = urlopener.open( uri )
> File "/usr/lib64/python2.6/urllib2.py", line 397, in open
> response = meth(req, response)
> File "/usr/lib64/python2.6/urllib2.py", line 510, in http_response
> 'http', request, response, code, msg, hdrs)
> File "/usr/lib64/python2.6/urllib2.py", line 435, in error
> return self._call_chain(*args)
> File "/usr/lib64/python2.6/urllib2.py", line 369, in _call_chain
> result = func(*args)
> File "/usr/lib64/python2.6/urllib2.py", line 518, in http_error_default
> raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
> HTTPError: HTTP Error 404: Not Found
>
> When I enhanced the log output like this:
> log.exception( "Error attempting to get tool shed status for installed
> repository %s (%s) (%s): %s" % ( str( repository.name ), str(tool_shed_url),
> str(url), str( e ) ) )
> I saw this in the log:
> tool_shed.util.shed_util_common ERROR 2013-10-14 09:55:26,584 Error
> attempting to get tool shed status for installed repository emboss_datatypes
> (http://toolshed.g2.bx.psu.edu)
> (http://toolshed.g2.bx.psu.edu/repository/status_for_installed_repository?name=emboss_datatypes&owner=devteam&changeset_revision=a89163f31369):
> HTTP Error 404: Not Found
>
> It occurs to me that the main toolshed may not be running with this
> feature enabled yet, and perhaps I should just ignore this error for
> now? (I'd like to be running the development branch for other
> features it gives me. Alternatively, I could think about back-porting
> the features I really need to stable, but that sounds like more work
> than I have time for.)
>
> When's the next stable release planned to be released, and what should
> I expect to be in it?
>
> 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/
