-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Add influxdb errors to pkger service error handling #16313
Labels
Comments
jsteenb2
added a commit
that referenced
this issue
Dec 22, 2019
this provides influxdb.Errors whenever possible from the pker service layer. the behavior that caused the error is somewhat implicated in the errro code. it is not perfect but is a big step forward. using the http server/client to run pkger stuff makes it abundantly clear the errors need to be communicated better. closes: #16313
3 tasks
jsteenb2
added a commit
that referenced
this issue
Dec 23, 2019
this provides influxdb.Errors whenever possible from the pker service layer. the behavior that caused the error is somewhat implicated in the errro code. it is not perfect but is a big step forward. using the http server/client to run pkger stuff makes it abundantly clear the errors need to be communicated better. closes: #16313
jsteenb2
added a commit
that referenced
this issue
Dec 23, 2019
this provides influxdb.Errors whenever possible from the pker service layer. the behavior that caused the error is somewhat implicated in the errro code. it is not perfect but is a big step forward. using the http server/client to run pkger stuff makes it abundantly clear the errors need to be communicated better. closes: #16313
jsteenb2
added a commit
that referenced
this issue
Dec 23, 2019
this provides influxdb.Errors whenever possible from the pker service layer. the behavior that caused the error is somewhat implicated in the errro code. it is not perfect but is a big step forward. using the http server/client to run pkger stuff makes it abundantly clear the errors need to be communicated better. closes: #16313
alexpaxton
pushed a commit
that referenced
this issue
Jan 9, 2020
this provides influxdb.Errors whenever possible from the pker service layer. the behavior that caused the error is somewhat implicated in the errro code. it is not perfect but is a big step forward. using the http server/client to run pkger stuff makes it abundantly clear the errors need to be communicated better. closes: #16313
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
right now the pkger service isn't returning great errors outside the parser errors. This issue is to update the service errors to be uniform and utilize the influxdb.Error type to provide errors across functional boundaries.
The text was updated successfully, but these errors were encountered: