Skip to content

Attempt using go mod vendor without creating go.mod#3045

Closed
errordeveloper wants to merge 3 commits intomoby:masterfrom
errordeveloper:go-mod-vendor-only
Closed

Attempt using go mod vendor without creating go.mod#3045
errordeveloper wants to merge 3 commits intomoby:masterfrom
errordeveloper:go-mod-vendor-only

Conversation

@errordeveloper
Copy link
Copy Markdown
Contributor

No description provided.

Comment thread vendor.mod
go 1.17

require (
code.cloudfoundry.org/clock v1.0.0
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did this one work with v1.0.0 ? I recalled they tagged 1.0.0 (without v prefix, and therefore go modules didn't see that as a release); https://github.com/cloudfoundry/clock/releases/tag/1.0.0

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They've made two tags actually 1.0.0 and v1.0.0: https://github.com/cloudfoundry/clock/tags

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh 🤦 how did I miss that? Perhaps I'm confused with another repository

Comment thread vendor.mod
github.com/container-storage-interface/spec v1.2.0
github.com/coreos/etcd v3.3.25+incompatible
github.com/docker/distribution v2.7.1+incompatible
github.com/docker/docker v20.10.3-0.20210720110456-471fd2770977+incompatible
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't checked, so just a random comment; did you manually specify the same commits (and/or versions) for each of these, or just let go modules find versions? (I expect "some" will be upgraded through indirect dependencies, which we can't prevent, but as long as we're mostly at the same version, that would be great (and we can handle upgrades later where we see fit)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't specify anything, I put exact commands in commit messages...

@@ -1,10 +0,0 @@
#include <stdio.h>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting that go modules discards c files here; wondering if that's gonna be an issue 🤔 (for these, it's probably fine, I think these are only used for integration tests in moby, so vndr may have just been overly cautious)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I don't think these can be recognised by go build in any way...

@codecov
Copy link
Copy Markdown

codecov Bot commented Dec 9, 2021

Codecov Report

Merging #3045 (9ea3f2b) into master (a9a35e0) will decrease coverage by 0.00%.
The diff coverage is n/a.

❗ Current head 9ea3f2b differs from pull request most recent head f20198c. Consider uploading reports for the commit f20198c to get more accurate results

@@            Coverage Diff             @@
##           master    #3045      +/-   ##
==========================================
- Coverage   62.15%   62.15%   -0.01%     
==========================================
  Files         155      155              
  Lines       24533    24533              
==========================================
- Hits        15249    15248       -1     
- Misses       7686     7689       +3     
+ Partials     1598     1596       -2     

@errordeveloper
Copy link
Copy Markdown
Contributor Author

closing this in favour of #3046

@errordeveloper errordeveloper deleted the go-mod-vendor-only branch December 9, 2021 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants