network explorer doesn't report backend failures to end user
Bug #1414975 reported by
John-Magne Bredal
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Network Administration Visualized |
Fix Released
|
Medium
|
John-Magne Bredal | ||
Bug Description
When expanding a node in Network Explorer fails, the spinner is left spinning as if it is still working on fetching data. This is misleading. If an error occurs, the spinning should stop and the user should be notified that the request failed.
| Changed in nav: | |
| importance: | Undecided → Medium |
| assignee: | nobody → John-Magne Bredal (john-m-bredal) |
| milestone: | none → 4.2.3 |
| status: | New → Confirmed |
Revision history for this message
| John-Magne Bredal (john-m-bredal) wrote | #1 |
| Changed in nav: | |
| status: | Confirmed → Fix Committed |
| summary: |
- network explorer error reporting + network explorer doesn't report backend failures to end user |
| Changed in nav: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix here:
https:/