-
Notifications
You must be signed in to change notification settings - Fork 42
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
Bug: not enough arguments in call to restmapper.NewShortcutExpander #319
Comments
Seems to be because we use v0.29.0 of client-go and kubedog uses v0.26.2, so the signature of the function has changed. How often do you integrate updates of dependencies here? |
Hi, thanks for the report! I think we can arrange client-go upgrade asap during this week. |
@very-doge-wow Hi! Just updated client-go to 1.29 #320, check it out! |
Thanks, will try it after the holidays. |
Have tested and it works now, thanks. Still the question, how often do you integrate updates? |
I am also receiving the following warning, not sure how to fix this:
Any advice? 🤔 |
@very-doge-wow Hi! As for your question: we are about to setup our periodical routine to update dependencies once in 3 or 4 weeks (security updates should be merged asap of course). It is important to know that kubedog project being used by such projects as: werf/werf and werf/nelm, and sometimes some dependencies updates may be blocked by these projects, but we are currently on a way to cleanup some old stuff from werf and keep dependencies as fresh as possible.
This is just harmless warning from inside client-go internals, which is part of it normal operation. However if you want to suppress these messages see this logger initialization snippet:
https://github.com/werf/kubedog/blob/main/cmd/kubedog/main.go#L72C13-L72C24 |
I'm trying to use the library as specified in: https://github.com/werf/kubedog/blob/main/doc/usage.md#examples-of-using-trackers
However I always receive this error:
This is my code:
I am using the most current version v0.11.0. Any help would be appreciated.
The text was updated successfully, but these errors were encountered: