Difference between revisions of "Galaxy Known Issues"
Jump to navigation
Jump to search
Moskalenko (talk | contribs) |
Moskalenko (talk | contribs) |
||
| Line 4: | Line 4: | ||
2012-10-04: | 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. | * 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. | ||
2012-09-01: | 2012-09-01: | ||
* BEAST wrapper tree and log file name handling is unstable. We're working on a long-term fix. Please email the [mailto:galaxy@hpc.ufl.edu Galaxy Administrator] if you need a short-term fix i.e. recovery of the output files for a job you already ran. | * BEAST wrapper tree and log file name handling is unstable. We're working on a long-term fix. Please email the [mailto:galaxy@hpc.ufl.edu Galaxy Administrator] if you need a short-term fix i.e. recovery of the output files for a job you already ran. | ||
Revision as of 21:01, 8 October 2012
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.
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.
2012-09-01:
- BEAST wrapper tree and log file name handling is unstable. We're working on a long-term fix. Please email the Galaxy Administrator if you need a short-term fix i.e. recovery of the output files for a job you already ran.