Red Hat Bugzilla – Bug 999876
Ugly, unformatted error pop-ups with stacktraces
Last modified: 2016-07-31 21:15:33 EDT
Created attachment 789111 [details]
Description of problem:
See screenshot. Someone is obviously trying to make it nicer with HTML tags. Those, unfortunately, seem to be escaped and are shown as well as the error message.
The stack trace should probably be kept in the server log, not shown to a business user.
The error pop-up should contain a message that would make sense for a business user.
So far, I've seen this while reproducing bug 999857 and bug 999874, though I'm sure these are not the only occurences.
Version-Release number of selected component (if applicable):
Looks like the error handling for XLS Decision Tables (and XLS Score Cards) needs some improvement. Thanks for reporting.
*** Bug 1007274 has been marked as a duplicate of this bug. ***
HTML tags are no longer escaped, true, unfortunately, the issue persists.
There's the stack trace, no business-user-friendly message plus the formatting is a bit unfortunate as there is a small error dialog half-way filled with h1 text "JBWEB000065: HTTP Status 500 -". If I, as a user, do something wrong, like try to create a XLS DT without selecting a file first, I want to see a reasonable message in the error pop-up. Something along the lines of what happened/failed + why + what to do. No stack trace and user friendly formatting.
OK, I understand. I thought it was just the formatting that you objected to. Anyway, the user now receives an error popup giving a clear message should they either fail to select a file, or select a file that is not a supported type. We have also improved the error reporting from the server.
The changes to improve error reporting were made against https://bugzilla.redhat.com/show_bug.cgi?id=1009358 and https://bugzilla.redhat.com/show_bug.cgi?id=1019842.
I have to return this once more.
See bug 1007437 - would it be possible to look at all the places dealing with error pop-ups and fix this completely?
QE considers this optional for 6.0.1.
I've tried with the various use-cases I can glean from the various BZs raised for this issue however I cannot replicate with the latest codebase (6.0.1.ER2). Please re-try.
If there is a specific example you still have where an ugly message is shown could you please provide details of exactly what it is you're doing?
Just found another occurrence in 6.0.1 CR1 BPMS:
If a jar upload fails, you get this again. Try especially with a jar containing a bad pom.xml - aim for "Unable to parse File 'pom.xml'".
Created attachment 977859 [details]
the way that the generic error is displayed
I have been trying to replicate this commented behaviour. I found that in many places in product the error message is shown in a ugly format, because the exception message is displayed but the html tags are used. Maybe the error classification could be more accurate but those message have to be displayed to help the user to understand and resolve the problem.
An improvement could be develop a new error popup with a link to details, and then the whole information could be displayed.