Difference between revisions of "Galaxy Known Issues"

From UFRC
Jump to navigation Jump to search
(Is this still relevant?)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:Galaxy]]
 
[[Category:Galaxy]]
 +
[[Category:AlexReview]]
 +
 
List of the issues with the UF Galaxy that we are aware of and are actively working on or have them in the queue to address later. Some of these issues are due to the the bugs in the Galaxy code provided by the Galaxy Team. Others are UF Galaxy specific. Please check this page before submitting a new support request ticket.
 
List of the issues with the UF Galaxy that we are aware of and are actively working on or have them in the queue to address later. Some of these issues are due to the the bugs in the Galaxy code provided by the Galaxy Team. Others are UF Galaxy specific. Please check this page before submitting a new support request ticket.
  
2013-01-02:
+
2013-01-31:
* Opening the shared 'Incoming' library can take a minute or so. It's a known Galaxy issue. The core team is working on addressing it in a future release.
+
* Uploading a composite "lped" dataset type is broken when jobs are run under a real user id. The core team is working on addressing the issue.
2012-10-04:
 
* Velvet wrapper is broken. It doesn't work with the real user id jobs. This problem has been reported to the Galaxy Team and will hopefully be addressed in the next code release.
 
2012-09-21:
 
* There are some browser specific JavaScript issues in using the Galaxy History. We'll keep looking for a fix coming from the Core Team.
 

Latest revision as of 21:08, 5 April 2018


List of the issues with the UF Galaxy that we are aware of and are actively working on or have them in the queue to address later. Some of these issues are due to the the bugs in the Galaxy code provided by the Galaxy Team. Others are UF Galaxy specific. Please check this page before submitting a new support request ticket.

2013-01-31:

  • Uploading a composite "lped" dataset type is broken when jobs are run under a real user id. The core team is working on addressing the issue.