Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exception is not communicated #5

Open
wolfc opened this issue Sep 20, 2013 · 4 comments
Open

Exception is not communicated #5

wolfc opened this issue Sep 20, 2013 · 4 comments

Comments

@wolfc
Copy link
Member

wolfc commented Sep 20, 2013

Permaine clicked 'Subscribe' on EAP View, but got:

Error with subscirbe operation
500 The call failed on the server; see server log for details

(Note the typo ;-) )
@ghost ghost assigned navssurtani Sep 20, 2013
@navssurtani
Copy link

Duplicate of #4?

@navssurtani
Copy link

Rather, the fix for #4 which is already in, should fix this issue?

@wolfc
Copy link
Member Author

wolfc commented Sep 23, 2013

No, #4 is about getting a correct cause (in log). This one is about communicating the error to the user.

@TomasHofman
Copy link
Contributor

I believe exceptions are now shown to user in most cases, as well as logged to a log file. Though this could be verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wolfc @navssurtani @TomasHofman