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.

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

General Exception Handling #8

Open
Ragora opened this issue Mar 24, 2016 · 3 comments
Open

General Exception Handling #8

Ragora opened this issue Mar 24, 2016 · 3 comments

Comments

@Ragora
Copy link
Contributor

Ragora commented Mar 24, 2016

The way the exceptions are dealt with in the current programming is a nightmare to debug. Exceptions are caught and reraised in plenty of locations which hides the origin of the original exception. Further, the way server exceptions are currently dealt with in some cases is to never print anything to server console and delegate it to the client with significant loss of information.

@Ragora Ragora changed the title Exception Handling General Exception Handling Mar 24, 2016
@atmafox
Copy link
Member

atmafox commented Mar 24, 2016

Ouch! This one's a big one and could greatly impair our ability to debug the software -- remember, we are in strict maintenance mode with this. What's the time investment to improve this?

@Ragora
Copy link
Contributor Author

Ragora commented Mar 24, 2016

I'm not quite sure on that one, the exception reraising complicates things significantly.

@Ragora
Copy link
Contributor Author

Ragora commented Mar 25, 2016

It's caused me all sorts of hell tracking #4 at this point. Hopefully everything works out in the server, dang.

@Delsorou Delsorou self-assigned this Mar 27, 2017
@Delsorou Delsorou modified the milestone: Revival-v0.1 Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants