You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Now we use install-go.sh to vendor golang version from the version at go.mod
What you expected to happen:
So project is stick with the version there.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Thing is we may not need it, since it looks like go compiler do a switch back to lang version
specified at go.mod [1] [2] [3].
Let's check if compiling failes if we add 1.13 errors Wrapf and build with golang 1.13.
What happened:
Now we use install-go.sh to vendor golang version from the version at go.mod
What you expected to happen:
So project is stick with the version there.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Thing is we may not need it, since it looks like go compiler do a switch back to lang version
specified at go.mod [1] [2] [3].
Let's check if compiling failes if we add 1.13 errors Wrapf and build with golang 1.13.
[1] golang/go#30603
[2] https://golang.org/cmd/go/#hdr-The_go_mod_file
[3] golang/go#28221
Environment:
NodeNetworkState
on affected nodes (usekubectl get nodenetworkstate <node_name> -o yaml
):NodeNetworkConfigurationPolicy
:kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'
):nmcli --version
)kubectl version
):The text was updated successfully, but these errors were encountered: