Syndesis: Improve error reporting in UI

[zregvart]

This is a...

[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Documentation issue or request

Description

Several times now I've found myself unable to troubleshoot an issue in the UI here's what usually happens: I get the _Something is wrong An error occurred while talking with the server. Please check your internet connection._, there's no error that can be seen in the Network or in the Console tabs of the developer tools.

Obviously some error occurred, doubtfully it has anything to do with the the server, I'm left with nothing to troubleshoot this. I wonder what happens when we get users reaching error states and we can't offer any ways to help them provide us with enough information to troubleshoot issues.

To me this is a blocking issue.

[riccardo-forina]

Was the error screen the one without the sidebar? That one has only one failure point, the app couldn't retrieve the config.json.

[zregvart]

Yeah, only error was shown without the sidebar. Though I had this happen before with the UI fully loaded, for instance in #5831 and the only way to troubleshoot that was to enable break-on-exception breakpoint and look through the obfuscated code/stack trace.

[riccardo-forina]

Oh I missed that issue. That error ui is another one tho, and it does support showing the stack trace; that’s it if the error is passed to it at least. We have not been consistent on that, I’ll amend in a new PR

[asmigala]

I just ran into this on 1.7.8:

Is the error screen supposed to be completely gone, or is the resolution here that there is an error in the console?

[heiko-braun]

@riccardo-forina I guess this a question for you.

[gashcrumb]

"Show error details" there would be relevant in this case I think, it's some kind of unexpected exception.

[gashcrumb]

BTW, I think @riccardo-forina's PR was more about ensuring that "Show error details" button is available vs. avoiding problems, so if that's some reproducible issue it should go into a new bug report.

[asmigala]

Couldn't reproduce the issue I showed above and the error pages now have "Show error details" button which does show some details, closing