> Ahhh ... Thanks .. I can't believe I missed that. Thanks for spotting it.
No problem!
> I'm not sure I understand enough about how this works to answer your
> ruby_home question. Ill play with this more tomorrow and see how things work
> with my tools and maybe have more feedback then
Sure
Ahhh ... Thanks .. I can't believe I missed that. Thanks for spotting it.
I'm not sure I understand enough about how this works to answer your ruby_home
question. Ill play with this more tomorrow and see how things work with my
tools and maybe have more feedback then
Cheers
Ira
> On 29 Oct 2
Hi Ira,
as far as I can see you missed the tag. That results in no log
message at all, since no action type is executed. Galaxy should probably
give an error here. Or better validate that during tool upload. I will
fill a Trello Card for it.
The following code snipped worked for me:
Hi Bjoern,
Thanks ... I thought I had to do that in order to make the GALAXY_RUBY_HOME
variable available ... nice that it's not necessary.
I've updated the tool on the test toolshed and have rerun my test but
unfortunately the problem is still there.
Cheers
Ira
On 29/10/2013, at 10:06 AM,
Hi Ira,
I can reproduce that error here, will try to study it tomorrow more
deeply. For the meantime can you try to remove the following lines?
It's not necessary.
Will get back to you tomorrow.
Bjoern
> Hi All,
>
> The
Hi All,
The short version of my problem is that I often seem to find myself in a
situation where my tool gets stuck in the "Installing" phase ... and I don't
know how to get feedback on it to see where it is failing. What I guess I'm
after is just the stdout of the tool installation .. but sin
