-
Notifications
You must be signed in to change notification settings - Fork 2
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
RSS Bot - If an RSS feed is unavailable during bot startup, the bot will crash and not start #36
Comments
How to reproduce from Regression Tests: Just set the file to map to a non-existing file. The test server will report an exception, and the client will throw one as well. |
Let's just get rid of the FailOnPluginFailure argument and always "crash" if a plugin fails. When a plugin fails, we should always exit and have the user unload plugins. No one reads the logs. |
There's more to this one as well. If the RSS should fail, we should not crash. Instead, when we check for updates, we should not send any messages if we got no updates because a site is down. |
Fixed a long-standing issue where if an exception happened while loading plugins, the bot would hang. Turns out, we weren't cleaning up some things properly. Specifically, EventScheduler. This has been resolved. * Added new Regression test to ensure the process exits if an assembly is missing. * We throw an exception if an assembly fails to load or init. Its just easier that way. * EventSchedule does not start until the IRC Connection is started. * Updated Regression Test Fixtures such that it is able to not wait for Chaskis to connect.
Automated test written. Closing issue. |
Found when starting up Chaskis when a website was down.
The RSS bot crashed during initialization. This caused the entire Bot to stop.
Stack Trace:
The text was updated successfully, but these errors were encountered: