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

Error recovery strategies #33

Open
4 tasks
brenns10 opened this issue May 3, 2017 · 0 comments
Open
4 tasks

Error recovery strategies #33

brenns10 opened this issue May 3, 2017 · 0 comments

Comments

@brenns10
Copy link
Owner

brenns10 commented May 3, 2017

It is currently possible for the bot to (almost) silently crash. The only evidence of this is the fact that the slacksoc user is no longer "online" according to Slack. We can do a number of things to avoid this.

  • Recover from panics at top-level function. I don't know if this will do much, because I'm sure that Go already outputs as much information as you could want when a panic crashes a program.
  • Recover from panics at plugin level, at least long enough to log them.
    • it could even be possible to make plugin registration reversible, and then unregister any plugin which causes a panic, to avoid further damage
  • Catch errors that are returned by plugin functions, and log them.
  • Add a logging hook that sends error/critical messages to slack (if possible), and maybe an email
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

1 participant