Greg,
I was mistaken. It wasn't a GET, it was a POST. Here's the POST
request:
POST /admin_toolshed/prepare_for_install?
includes_tools_for_display_in_tool_panel=Trueencoded_repo_info_dicts=72
2fdbb60840f8caa6f7dd248a9f08b927df4325%
Hi Rico,
This should be fixed in 10742:3de162c29e7e.
Thanks for reporting this,
Greg Von Kuster
On Sep 27, 2013, at 12:18 PM, Richard Burhans r...@bx.psu.edu wrote:
Greg,
I was mistaken. It wasn't a GET, it was a POST. Here's the POST request:
POST
Hi Rico,
Can you provide the specific GET request URL with which you encountered this
problem? There are very few GET requests when installing repositories from the
tool shed - the only one I can locate without a lot of digging is the
following, which I don't think is causing the problem.
#
Folks,
After checking a little closer last night, I have one clarification.
The Tool Shed does use POSTs as well as GETs, but even when it's
POSTing, the encoded dictionaries (encoded_repo_info_dicts) are part
of the query string. The encoded_repo_info_dicts should probably
become part of the
When installing Galaxy Tool Shed repositories into a local Galaxy
instance, tool shed dependecies are exchanged as an encoded python
dictionary via the HTTP GET method.
If a tool shed repository contains enough dependencies, the length
of this encoded dictionary can become extremely long. In my
