You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
The text was updated successfully, but these errors were encountered: