Hi Carl!

Exverything is okay by now. Thanks for your support!

Cheers,

Sascha

Sascha, 

As of the latest revision, the display button has been re-added for datasets in the error state.

The ’edit attributes’ button has been re-added for error’d datasets as well.

Let me know if you see any other problems with the history panel and thanks,

Carl

On Wed, Nov 21, 2012 at 11:03 AM, Carl Eberhard <carlfeberhard@gmail.com> wrote:

Hi Sascha and Ted,

The history panel is undergoing some major revisions and the omission of the display icon was part of that. It will be re-added today.

Information from a jobs stdout and stderr are still be available using the ’i’nformation icon within each history item’s display (You’ll see a ’Show details’ bit of help text when you hover your mouse over the icon; clicking on it will bring up a page with links to display both stdout and stderr). We’ll definitely consider a more extensive error dataset but it may not be feasible at the moment.

Thanks,

Carl

On Tue, Nov 20, 2012 at 1:59 PM, Ted Goldstein <ted@soe.ucsc.edu> wrote:

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/