-
Notifications
You must be signed in to change notification settings - Fork 15
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
Consider some mechanism for handling worker errors in the default client? #22
Comments
Hey @ccahoon, thanks for the great writeup and I'm sorry for taking so long to get back to you! I think we can definitely implement one or both of these solutions. I'm doing some work this week to remove the metrics code (see our blog post), so that should simplify the first option. I'll think about this a bit more and then work on it after the metrics removal. |
Great to hear! Congratulations on the code deletion—it's one of my favorite things. I ran into a case last night where I got a lot of errors dropped (it was fine, they were all the same anyway) and I might have handled it better with one of these mechanisms. It feels nice at least to know that there's a concrete use case and that I'm not just asking you to do work for hypotheticals =). |
Update on this: (obviously) I haven't had time to work on it. I think the adding a If anyone wants to work on either of these two things, let me know. Otherwise I'll get to it eventually. I'm going to close this issue and create a separate one for adding the |
Hello!
First of all, thanks for the great service and the great Go client.
I have not been able to find an existing mechanism in the library to be able to take action in the case of a worker failure in the default client, for example due to network issues (say, my server is unable to connect to Honeybadger's API).
I am able to work around it with your current implementation, but my solution feels a bit hackish. I am wrapping the Notify method of the default server backend so that I can do something when it fails (since errors that get returned to workers just get logged).
So, I have two possible proposals:
I don't have a strong opinion—I didn't want to just write a feature request without trying to think it through. Either of these would solve the issue I'm having, and I think that it would be nice if the library provided access to worker errors in some fashion.
Thanks!
The text was updated successfully, but these errors were encountered: