Actions
Bug #4938
closed[Workbench] improve error reporting for failed AJAX calls
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Start date:
01/08/2015
Due date:
% Done:
0%
Estimated time:
Story points:
1.0
Description
Example, after running pipeline https://workbench.qr1hi.arvadosapi.com/pipeline_instances/qr1hi-d1hrv-kg7ndj85njzpt1x and waiting for it to finish:
Files
Updated by Brett Smith about 10 years ago
This is the same message seen in #4776, so addressing this will likely help that along.
Updated by Tom Clegg about 10 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.
Updated by Tom Clegg about 10 years ago
- Target version changed from Bug Triage to 2015-02-18 sprint
Updated by Tom Clegg about 10 years ago
- Target version changed from 2015-02-18 sprint to Arvados Future Sprints
Updated by Ward Vandewege almost 4 years ago
- Target version deleted (
Arvados Future Sprints)
Actions