Let me echo Sascha. I've been thinking about this problem. I suggest that we need an "Error Document" dataset type that contains two kinds information: 1. which will help the end user correct the problem (E.g. Please be sure to use MAF files not BAM files etc). 2. which will help tool developers collect a bunch of log files..
Error Documents could be aggregated (especially useful in a cluster computation). Then the report a bug button would aggregate the log file document and send it to the tool developer. Before sending, the end user would be able to see the contents and be sure that they were not posting confidential information offsite. Thanks Ted On Nov 20, 2012, at 8:02 AM, MSc. Sascha Kastens wrote: > Hey devs! > > It seems that many things related to history datasets has changed since I > have updated my local Galaxy instance and > the current version. > > Unfortunately it seems that one cannot "Display data in browser" (eye icon) > if the dataset is in error state. Where can I > get that feature back? Some of my tools write logging information to a > separate logfile which will be in error state if > the tool fails but contain useful information. > > Thanks, > > Sascha > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/