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
chore: bump google cloud storage #3676
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3676 +/- ##
=======================================
Coverage 56.58% 56.58%
=======================================
Files 103 103
Lines 7520 7520
=======================================
Hits 4255 4255
Misses 2596 2596
Partials 669 669 Continue to review full report at Codecov.
|
Looks like there's an issue with the
edit: I tried git diff
diff --git a/go.sum b/go.sum
index 27e9e064..fa2d82b6 100644
--- a/go.sum
+++ b/go.sum
@@ -106,7 +106,6 @@ github.com/bugsnag/osext v0.0.0-20130617224835-0dd3f918b21b/go.mod h1:obH5gd0Bsq
github.com/bugsnag/panicwrap v0.0.0-20151223152923-e2c28503fcd0 h1:nvj0OLI3YqYXer/kZD8Ri1aaunCxIEsOst1BVJswV0o=
github.com/bugsnag/panicwrap v0.0.0-20151223152923-e2c28503fcd0/go.mod h1:D/8v3kj0zr8ZAKg1AQ6crr+5VwKN5eIywRkfhyM/+dE=
github.com/census-instrumentation/opencensus-proto v0.2.1/go.mod h1:f6KPmirojxKA12rnyqOA5BBL4O983OfeGPqjHWSTneU=
-github.com/cespare/xxhash v1.1.0 h1:a6HrQnmkObjyL+Gs60czilIUGqrzKutQD6XZog3p+ko=
github.com/cespare/xxhash v1.1.0/go.mod h1:XrSqR1VqqWfGrhpAt58auRo0WTKS1nRRg3ghfAqPWnc=
github.com/cespare/xxhash/v2 v2.1.1/go.mod h1:VGX0DQ3Q6kWi7AoAeZDth3/j3BFtOZR5XLFGgcrjCOs=
github.com/cespare/xxhash/v2 v2.1.2 h1:YRXhKfTDauu4ajMg1TPgFO5jnlC2HCbmLXMcTG5cbYE= |
I'm curious though; do you have more details about this? I see CI on this repository is using Go 1.18; is it failing on 1.19beta1 or 1.18? |
actually i'm still on Go 1.17.10, I believe vendoring might not work the same based on the go version. Locally, Yes, it seems go.sum gets updated, i haven't pushed an update since validate-vendor still fails for me. |
Both should be running inside a Dockerfile, so afaics, the host environment should not make a difference; Lines 106 to 114 in 26a586c
Could it be you tried to run |
bd310f2
to
e1f5c29
Compare
this is probably right. I haven't run |
It seems the logic in |
Are you saying that there are additional changes required before users can compile for google cloud and use google cloud storage for their registry? If so, I'd suggest making this a draft PR. |
according to the comments in https://github.com/distribution/distribution/blob/main/registry/storage/driver/gcs/gcs.go#L317-L318, the logic was copied from an outdated google cloud storage api. I believe this logic needs to be updated as well. |
Yes, I don't think the Google cloud storage driver is working. I expect it's not worth merging this PR until the work to fix it is done. Are you planning to work on it? |
i'll have a look and see how to convert current logic with latest api code |
Are there other plugins that are optional (and thus not compiled by default)? If so, we should have a job in CI that at least tries to compile the binaries with those build-flags set (so that we can see when things break) We should also list the available build-tags (and their meaning) under https://github.com/distribution/distribution/blob/main/BUILDING.md#optional-build-tags |
I was thinking of doing that the other day. See #3687 |
@@ -15,7 +15,6 @@ import ( | |||
"golang.org/x/oauth2" | |||
"golang.org/x/oauth2/google" | |||
"google.golang.org/api/googleapi" | |||
"google.golang.org/cloud/storage" |
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.
No replacement storage import here.
@thaJeztah are you opening a PR for this? |
I would be interested in helping with this PR. Let me know if you have something I can help with. |
I think the important thing is getting the storage driver working. Until it's working it's not even worth turning it on in ci or changing dependencies. |
I have a PR started at kaovilai#1 It's a mess, needs cleanup, but the only thing failing at the moment is:
Trying to figure out what's going wrong, but not really certain atm. |
Keep an eye on #3702 |
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. @thaJeztah can you double check if I missed anything, please 🙇
@bshaaban do you want to remove |
@milosgajdos I don't think this PR is doing anything. Merging this will still result in broken, non-compiling GCS code. The CI is passing because BUILDTAGS hasn't been passed to |
This PR is still WIP per comment |
Will mark this as draft. |
I can rebase on top of #3702 to maintain dep updates since gcs was updated there already. |
This change updates google cloud dependency as the current version dates back to a 2015 version and does not compile with the latest Go version closes distribution#3668 Signed-off-by: Bahaiddine A <bshaaban@mirantis.com>
c4767c2
to
b415ab0
Compare
closing this pr, in favor of #3702 |
This change updates google cloud dependency as the current version dates back to a 2015 version and does not compile with the latest Go version
closes #3668
Signed-off-by: Bahaiddine A bshaaban@mirantis.com