-
Notifications
You must be signed in to change notification settings - Fork 422
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
Error Handling Improvements (all errors should gracefully fail) #421
Comments
In regards to #419, shouldn't a On topic: Are we talking about just.. wrapping the whole thing into a |
Lines: 747-753:
At a minimum what I'm thinking is we take these lines and instead of throwing an error after the hail mary, we send the error message to console, and make a threshold. If we see 3-5 errors in less then 5 seconds then we throw the err. To your idea, maybe wrapping try catch to every case would be a good idea. It might help vet out other things, possibly a good excuse to crawl through the code again. |
I'd do a "lets first close all the PRs" motion before handling this refactor, but we are on the same page on this one :) |
Fine by me. |
I purpose to improve error handling to prevent crashing as much as programmatically possible during normal operations.
The text was updated successfully, but these errors were encountered: