vendor: eliminate some of the replace directives#3048
vendor: eliminate some of the replace directives#3048errordeveloper wants to merge 4 commits intomoby:masterfrom
replace directives#3048Conversation
0efc05e to
02fb360
Compare
Codecov Report
@@ Coverage Diff @@
## master #3048 +/- ##
==========================================
+ Coverage 62.14% 62.29% +0.14%
==========================================
Files 155 155
Lines 24533 24533
==========================================
+ Hits 15247 15282 +35
+ Misses 7682 7651 -31
+ Partials 1604 1600 -4 |
Could this be an issue with upgraded deps or is it a flake? 🤔 |
Ok, looks like a flake as it all tests passed on a previous commit. |
0c2ce7f to
a9ada03
Compare
crazy-max
left a comment
There was a problem hiding this comment.
Great! Minor nit, also squash commits
This comment has been minimized.
This comment has been minimized.
dd36e92 to
43f7d64
Compare
Files in GOPATH have read-only persmissions, after simply copying them can result in an access error. Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
43f7d64 to
25e88b5
Compare
Signed-off-by: Ilya Dmitrichenko <errordeveloper@gmail.com>
|
@thaJeztah I think we should merge this, when I update Moby I'll make sure to use 234cb83 in the first update. |
|
@errordeveloper moby/moby#43101 has been merged. I think we can move forward with this one. |
| gopkg.in/fsnotify.v1 v1.4.7 // indirect | ||
| gopkg.in/tomb.v1 v1.0.0-20141024135613-dd632973f1e7 // indirect | ||
| gopkg.in/yaml.v2 v2.4.0 // indirect | ||
| gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c // indirect |
There was a problem hiding this comment.
Was wondering why this didn't use a tagged release, but looks like no v3 releases exist yet; https://github.com/go-yaml/yaml/tags
There was a problem hiding this comment.
eh... also gopkg.in does some magic, which I never had the time to try and understand, very few libs use it anyway.
| replace ( | ||
| github.com/Microsoft/go-winio => github.com/Microsoft/go-winio v0.4.15 | ||
| github.com/akutz/gosync => github.com/akutz/gosync v0.1.0 | ||
| github.com/containerd/containerd => github.com/containerd/containerd v1.5.2 |
There was a problem hiding this comment.
Was this replace still needed? Wondering if we can just update the indirect dependency to the latest v1.5.x release
I should note that if we need to keep some of the replace rules, then it might be good to add a comment in the corresponding require section, and to add a comment that "the actual version is overridden in the replace section", similar to https://github.com/moby/buildkit/blob/390c6886f4a310af5ee0d45eaab35dc36b21f23e/go.mod#L22-L23
It's easy to overlook that there's a replace rule for a dependency, and people may then forget to update (or remove) them when updating dependencies.
There was a problem hiding this comment.
As the time of the PR states, the goal is to remove only some of the replace directives, i.e. seemingly trivial version bumps that won't affect downstream in any way. So runc and containerd are untouched for the purpose of this PR, as I cannot assume those are trivial and won't affect Moby.
| github.com/matttproud/golang_protobuf_extensions => github.com/matttproud/golang_protobuf_extensions v1.0.1 | ||
| github.com/onsi/ginkgo => github.com/onsi/ginkgo v1.8.0 | ||
| github.com/onsi/gomega => github.com/onsi/gomega v1.5.0 | ||
| github.com/opencontainers/runc => github.com/opencontainers/runc v1.0.0-rc95 |
There was a problem hiding this comment.
Same for this one; if we update containerd, this may not be needed (I see containerd 1.5.x now uses run v1.0.2); https://github.com/containerd/containerd/blob/v1.5.9/go.mod#L43
| @@ -120,9 +104,3 @@ replace ( | |||
| // After updating GRPC, if integration test failures occur, verify that the | |||
| // string matching there is correct. | |||
| replace google.golang.org/grpc => google.golang.org/grpc v1.23.0 | |||
There was a problem hiding this comment.
Do we need to / should we copy the replace rules from the containerd version we're using? Or does it break with v1.27.1 ? There's some other related replace in the containerd go.mod as well; https://github.com/containerd/containerd/blob/v1.5.9/go.mod#L75-L80
github.com/gogo/googleapis => github.com/gogo/googleapis v1.3.2
github.com/golang/protobuf => github.com/golang/protobuf v1.3.5
// urfave/cli must be <= v1.22.1 due to a regression: https://github.com/urfave/cli/issues/1092
github.com/urfave/cli => github.com/urfave/cli v1.22.1
google.golang.org/genproto => google.golang.org/genproto v0.0.0-20200224152610-e50cd9704f63
google.golang.org/grpc => google.golang.org/grpc v1.27.1
There was a problem hiding this comment.
This is another non-trivial one, so I'd leave it for another PR :)
There was a problem hiding this comment.
Yeah this is the hard one that blocks buildkit vendoring on moby.
There was a problem hiding this comment.
Yeah, we can do in a follow-up. I was looking at the moby code, which already included those replace rules (linking to the vendor.conf file for convenience) and versions of containerd/runc
- https://github.com/moby/moby/blob/79651b7a979b40e26af353ad283ca7ea5d67a855/vendor.conf#L83
- https://github.com/moby/moby/blob/79651b7a979b40e26af353ad283ca7ea5d67a855/vendor.conf#L76
For these I was more concerned about not having replace rules for some of them, but CI is green so at least currently it works 😂
|
@thaJeztah thanks for the review! |
|
@dperny PTAL 🤗 |
|
These have now all been removed in #3094 |
First follow-up to #3046 (comment)