Created attachment 1139594 [details] uncaught exception overload Description of problem: New uncaught exception notification repeats endlessly sometimes. Version-Release number of selected component (if applicable): 4.0 - master How reproducible: ? Steps to Reproduce: I'm not sure how to reproduce. This happened to me while applying an unrelated patch to test it. Actual results: see screenshot Expected results: The notification should be a single box. If they stack endlessly on top of each other, the app is obviously unusable. Additional info:
Each red box represents a separate occurence of (uncaught) UI error. Do we want to: 1, remember content of currently showing boxes and put a number next to existing one to indicate the number of occurences so far? 2, allow only one red box shown at a time? (this hides errors that occur in the meantime, until the current box is closed)
I like option 1. That's what browser dev tools do.
(In reply to Greg Sheremeta from comment #2) > I like option 1. That's what browser dev tools do. Me too, the implementation shouldn't be hard anyway.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Alexander, was it merged before 4.0.2 branch was created?
No it was not, I can backport if needed, but this is not something new, so I didn't think it was worth backporting.
Actually, just checked the 4.0.2 branch, and it was merged before the branch was created.
Verified in ovirt-engine-webadmin-portal-4.0.2.1-0.1.el7ev.noarch rhevm-4.0.2.1-0.1.el7ev.noarch If more than one UI exception occurs, only one alert box is shown with a counter on the right side. See attached screenshot for details.
Created attachment 1185157 [details] single exception alert with a counter