Bug #4938
closed
[Workbench] improve error reporting for failed AJAX calls
Added by Tim Pierce over 9 years ago.
Updated about 2 years ago.
Files
- Description updated (diff)
This is the same message seen in #4776, so addressing this will likely help that along.
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.
- Target version changed from Bug Triage to 2015-02-18 sprint
- Target version changed from 2015-02-18 sprint to Arvados Future Sprints
- Target version deleted (
Arvados Future Sprints)
- Status changed from New to Closed
Also available in: Atom
PDF