-
Notifications
You must be signed in to change notification settings - Fork 55
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
vai: log errors on add #120
Conversation
client-go unfortunately "swallows" them Signed-off-by: Silvio Moioli <silvio@moioli.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should get a review from people with more Vai knowledge (@ericpromislow?)
Does client-go "swallow" them because we don't set a klog log level high enough? Or are they really ignored? In any case, I feel like we should log for all cases anyway (add, update and delete)? |
Signed-off-by: Silvio Moioli <silvio@moioli.net>
Really ignored, unfortunately: (error is either ignored or pop is retried, but in no case logged)
Update is transitively covered by Add, Delete I have just added. Thanks |
Eagerly looking forward to this to help debug an issue indexing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That will definitely be useful, surprised those errors are ignored like that.
Co-authored-by: Tom Lebreux <me@tomlebreux.com>
Co-authored-by: Tom Lebreux <me@tomlebreux.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be some double-logging on these errors -- I count five calls from steve
to ….[Ss]tore.Delete()
at there might be others, where the method's receiver variable isn't called "store". All the calls I did fine do no logging, so better to put up with some double-logging and then unlogged errors.
client-go unfortunately "swallows" them
Partly addresses rancher/rancher#48384