Bug #4938

[Workbench] improve error reporting for failed AJAX calls

Added by Tim Pierce over 4 years ago. Updated over 4 years ago.

Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Story points:


Example, after running pipeline https://workbench.qr1hi.arvadosapi.com/pipeline_instances/qr1hi-d1hrv-kg7ndj85njzpt1x and waiting for it to finish:

arvados_error_message.png (47.4 KB) arvados_error_message.png Tim Pierce, 01/08/2015 06:07 PM

Related issues

Related to Arvados - Bug #4776: [Workbench] Pipeline pane load error when opening pipeline from home page in new browser tabClosed12/10/2014

Related to Arvados - Bug #5105: [Workbench] AJAX content loaders should not follow a redirect to the welcome page and use that as a partial, if token or session has been invalidatedResolved01/29/2015


#1 Updated by Tim Pierce over 4 years ago

  • Description updated (diff)

#2 Updated by Brett Smith over 4 years ago

This is the same message seen in #4776, so addressing this will likely help that along.

#3 Updated by Tom Clegg over 4 years ago

Specific improvements:
  • Default fall-back error message should be more friendly than "error". Perhaps: "Sorry, I don't have any further details about what the error was."
  • Try some other things before the fall-back. If there's an exception, a stack trace might be accessible (catch(e){var foo=e.stack}), and we can show the whole thing or part of it.
  • Show a "report an issue" button if the error came with an HTTP status code.
  • See if we can get a useful error message from the browser in the cases that are known to be common, like timeout.

#4 Updated by Tom Clegg over 4 years ago

  • Story points set to 1.0

#5 Updated by Tom Clegg over 4 years ago

  • Target version changed from Bug Triage to 2015-02-18 sprint

#6 Updated by Tom Clegg over 4 years ago

  • Target version changed from 2015-02-18 sprint to Arvados Future Sprints

Also available in: Atom PDF