-
Notifications
You must be signed in to change notification settings - Fork 372
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
make the formatting errors based on go 1.19 #758
Conversation
174c571
to
b16bd40
Compare
// - VolumsnapshotStatus is used by end users because they cannot see VolumeSnapshotContent. | ||
// - CSI snapshotter sidecar is light weight as it only watches VolumeSnapshotContent | ||
// object, not VolumeSnapshot object. | ||
// - Fields in VolumeSnapshotContentStatus can be used for filtering when importing a |
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.
Why does the code under vendor
change?
You said "lift the dependencies" - what exactly does that mean?
I don't see a version change in go.mod.
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.
I was referrring the update in client go.mod with version bump to kube v1.25 https://github.com/kubernetes-csi/external-snapshotter/pull/758/files#diff-de2c00fe7d49a7bb4d5c225eded980780a7b9dde4ae89e70c7e497cd0e45b15bL9-R6 by lift the dependencies
.
Please don't update anything in the client folder yet. |
IMHO all that this PR should do is make the formatting compliant with Go 1.19 and nothing else. Then we can merge kubernetes-csi/csi-release-tools#203. |
ok.. let me shrink the PR to just do formatting based on 1.19 in that case. |
@pohly @xing-yang as per the above discussion, I have kept only formatting change here in this PR. ptal.. Thanks.. |
/hold cancel |
7f07a0e
to
f5d0ee9
Compare
Can you remove the dependency update commit? It is unrelated to this PR. |
You probably added it because of a Trivy failure, but that's just bad style. I'm really getting annoyed by this security check. |
The Trivvy scnner fail here in this PR on lastest run, so clubbed with the same. I can split that to another PR too and mark it as dependency for this PR. |
Indeed . Thats why I refreshed with that change. Let me split that up first. |
9060b22
to
f5d0ee9
Compare
The trrivvy failure has been addressed here #759 |
Reference# kubernetes-csi/csi-release-tools#203 Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
f5d0ee9
to
d34102f
Compare
As the trivvy failure has been addressed on master, I have rebased this PR. This should be good to go as well @xing-yang @pohly |
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.
/lgtm
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: humblec, pohly, xing-yang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Humble Chirammal hchiramm@redhat.com
Additional Note for reviewer:
The errors in absence of this PR cause tests to fail in kubernetes-csi/csi-release-tools#203