I believe I have found a bug? Or maybe I'm not using Galaxy correctly? These
are the steps I used:
* Downloaded the latest version of Galaxy
* Created a user m...@me.commailto:m...@me.com
* Uploaded several files
* Logged out
* Create a user
Just double checking: Have you looked at the list of 'Saved Histories'?
For each user, you probably have several histories called 'Unnamed
history' and one of them may contain the data you uploaded previously.
Whenever you log out and log in as a different user, a new, empty
You are correct. When I look at the Save Histories and I double click
on them I can see everything.
Thanks for the help
From: Hans-Rudolf Hotz [mailto:h...@fmi.ch]
Sent: Friday, 17 May 2013 4:58 PM
To: Burdett, Neil (ICT Centre, Herston - RBWH)
Allright. I just pulled in all changesets from stable to my cloud
Galaxy, restarted, and everything works, at first glance.
Thanks for your support!
Rijvisschestraat 120, 9052 Zwijnaarde
Tel: +32 9 244.66.34
Bioinformatics Training and Services (BITS)
I have fired up an cloud instance of Galaxy, 2 persistent nodes,
scalable up to 10. I have updated the code to the latest stable, after
issues with not being able to select multiple input for workflows (more
I've realised that my current Blast2GO install script would be a perfect
example of where this tweak to fabric_util.py would help - when I wrote
the tool_dependencies.xml I didn't appreciate that the download_by_url
action was only allowed as the first action - currently it is ignored
Hi Greg Dave,
I just tried to upload an update to my Blast2GO wrapper on the Test Tool Shed,
This gave the following error, also note typo sucessfully [sic] - successfully.
Internal Server Error
Galaxy was unable to sucessfully complete
Thanks for letting me know and sorry about the inconvenience. I've fixed this
in 9763:9c06caa86e2a which is now on the test tool shed.
Greg Von Kuster
On May 17, 2013, at 5:08 AM, Peter Cock wrote:
Hi Greg Dave,
I just tried to upload an update to my Blast2GO wrapper on the
It is most likely due to the cluster configuration, since on our
non-cluster production machine doesn't have this behaviour.
Contact details: http://www.bits.vib.be/index.php/about/80-team
On 05/17/2013 10:16 AM, Joachim Jacob | VIB | wrote:
I have fired up
I developed a script to download file to Galaxy from other platform. If
the size of the file is large, the process may take several minutes and
I can't to anything else in Galaxy. Is there a way to add the download
process in a job handler and add it to history queue?
Any help is
On Fri, May 17, 2013 at 12:37 PM, Greg Von Kuster g...@bx.psu.edu wrote:
Thanks for letting me know and sorry about the inconvenience. I've fixed
this in 9763:9c06caa86e2a which is now on the test tool shed.
Greg Von Kuster
Great - that works for me now :)
Do you guys have a rough plan for when inter-ToolShed dependencies
will be supported?
I've been using the Test Tool Shed to validate tools before uploading
them to the main Tool Shed - this uncovers things like omitted test
files which I don't find locally since I'm testing in-situ.
I realized there was no Galaxy group on G+, although I find G+ is a
really nice medium for some kind of posts, especially for things like
showing off some work you have done, without disturbing others on the
Feel free to chime in:
There was a long conversation about this topic in IRC yesterday (among
people who don't actually use the tool shed all that frequently), I
have posted it to the new unofficial Galaxy Google+ group if anyone
would like to read and chime in.
All of a sudden, some larger libraries are taking a very long time to open.
This one timed out…
Anybody else seen this?
Could this be a database issue? Didn't see any really long queries in the
postgres log (and i log anything longer than
Mail list logo