Skip to content

feature: improve error reporting #48

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

Open
jainvipin opened this issue Apr 9, 2015 · 2 comments
Open

feature: improve error reporting #48

jainvipin opened this issue Apr 9, 2015 · 2 comments

Comments

@jainvipin
Copy link

When errors are not aggregated, it doesn't give a clear trace of who triggered the error and eventually where it failed. Aggregation of stacked errors that gets displayed like a backtrace is very useful. An implementation that attempts to aggregate the errors can be found in kubernetes (https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/util/errors/errors.go)

@gaurav-dalvi
Copy link
Contributor

@erikh : Can we close this issue if this is fixed ? Just digging older issues !

@erikh
Copy link
Contributor

erikh commented Aug 3, 2016

fwiw we did resolve this, it just never got integrated back into netplugin

On Tue, Aug 2, 2016 at 5:39 PM, Gaurav Dalvi [email protected]
wrote:

@erikh https://github.com/erikh : Can we close this issue if this is
fixed ? Just digging older issues !


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#48 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJ67cMR8Tsw_c0Jhg3A6IoeeJszyTnks5qb-MkgaJpZM4D9a7g
.

dseevr pushed a commit to dseevr-dev/netplugin that referenced this issue Nov 28, 2017
Add clustermode to GlobalOper
@erikh erikh removed their assignment Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants