go.mod: name packages with go.etcd.io/etcd/v3#11823
Conversation
a812af4 to
206fcf4
Compare
Codecov Report
@@ Coverage Diff @@
## master #11823 +/- ##
==========================================
- Coverage 66.29% 65.89% -0.40%
==========================================
Files 403 403
Lines 36984 36984
==========================================
- Hits 24517 24370 -147
- Misses 10980 11099 +119
- Partials 1487 1515 +28
Continue to review full report at Codecov.
|
|
Update: resolved in cf9c568 This is weird, consistently getting this error after all of this: |
206fcf4 to
925a9a7
Compare
This change makes the etcd package compatible with the existing Go ecosystem for module versioning. Used this tool to update package imports: https://github.com/KSubedi/gomove
Found potential locations via ``` git grep 'go.etcd.io/etcd$' ```
add go.etcd.io/etcd/v3 to existing filters
bill-of-materials: - update to new package names test/updatebom.sh scripts: - Update to the right package names - Don't add bom tool to go.mod
gofmt tests were failing, fix.
88da7b1 to
c9cdefa
Compare
|
Integration is failing on a test that almost certainly latency flakey: |
|
Have you tried to write a simple program with etcd/client dependency? |
|
What do you mean? What is it you are trying to test?
…On Tue, Apr 28, 2020, 8:29 AM Xiang Li ***@***.***> wrote:
@philips <https://github.com/philips>
Have you tried to write a simple program with etcd/client dependency?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11823 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAIGCB3QVJS456WYLNP6UDRO3Y4PANCNFSM4MRN5O7A>
.
|
Something like import go.etcd.io/etcd/v3/clientv3
func main() {
_, _ = clientv3.New(...)
...
}Just to make sure the client dependency can be resolved correctly outside the etcd project. |
|
I gave it a try. It seems working well. |
|
OK, thanks.
Does it all LGTY then?
…On Tue, Apr 28, 2020 at 9:01 AM Xiang Li ***@***.***> wrote:
I gave it a try. It seems working well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11823 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAIGCB22XXCKBISASNDNGDRO34UPANCNFSM4MRN5O7A>
.
|
|
LGTM |
|
cc @etcd-io/maintainers-etcd we should all take a look at this go.mod change |
gyuho
left a comment
There was a problem hiding this comment.
awesome, thank you so much!
|
I am going to merge this at 2pm Pacific today (Tues. 2020-04-28) if there
are no objections.
…On Tue, Apr 28, 2020 at 10:29 AM Gyuho Lee ***@***.***> wrote:
***@***.**** approved this pull request.
awesome, thank you so much!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11823 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAIGCAYGSU2KAXUOJHFSFLRO4HAPANCNFSM4MRN5O7A>
.
|
|
@philips Can we update https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.5.md in a separate PR (or just separate commit is good too)? |
|
i will add the changelog and try to fix markdown docs before merging |
Use the new package path in the docs and announce it in the CHANGELOG
with the merge of etcd-io/etcd#11823 etcd v3.5.0 will now have a properly imported versioned path this fixes our pending migration to newer repo
with the merge of etcd-io/etcd#11823 etcd v3.5.0 will now have a properly imported versioned path this fixes our pending migration to newer repo
with the merge of etcd-io/etcd#11823 etcd v3.5.0 will now have a properly imported versioned path this fixes our pending migration to newer repo
with the merge of etcd-io/etcd#11823 etcd v3.5.0 will now have a properly imported versioned path this fixes our pending migration to newer repo
with the merge of etcd-io/etcd#11823 etcd v3.5.0 will now have a properly imported versioned path this fixes our pending migration to newer repo
Attempt to fix #11820