You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the XXX_unrecognized cause issues here as well (see moby/swarmkit#2837 for the discussion on SwarmKit)
gometalinter --config .gometalinter.json ./...
73runtime\v2\runhcs\service.go:836:2:warning: too few values in struct literal (compile) (staticcheck)
74runtime\v2\runhcs\service.go:836:2:warning: too few values in struct literal (compile) (staticcheck)
75runtime\v2\runhcs\service.go:859:2:warning: too few values in struct literal (compile) (staticcheck)
76runtime\v2\runhcs\service.go:859:2:warning: too few values in struct literal (compile) (staticcheck)
77runtime\v2\runhcs\service.go:836:2:warning: unused struct field too few values in struct literal (structcheck)
78runtime\v2\runhcs\service.go:859:2:warning: unused struct field too few values in struct literal (structcheck)
79runtime\v2\runhcs\service.go:836:2:warning: too few values in struct literal (unconvert)
80runtime\v2\runhcs\service.go:859:2:warning: too few values in struct literal (unconvert)
81runtime\v2\runhcs\service.go:836:2:warning: unused variable or constant too few values in struct literal (varcheck)
82runtime\v2\runhcs\service.go:859:2:warning: unused variable or constant too few values in struct literal (varcheck)
@stevvooe if you have time; perhaps you could give this a look; looking for the changes in protobuf, I found discussions where you were on about preserving the "extra" fields; I wasn't sure if we wanted to keep them or discard them (downside of keeping them could perhaps be "more overhead" / memory?)
This may cause extra memory usage, but I don't think we necessarily want to turn off extras without a good reason. This change will cause a little extra memory bloat, so that may be reason enough.
Looking at the generated code, I don't see any causes for compatibility concerns. If you want to be sure, you can run the integration tests from an older checkout against a daemon built with these changes.
Thanks for looking! I saw they also have a v1.3.1 now, but taking it one step at a time (I think BuildKit was on 1.2.0, so although not related, trying to keep my deps a tiny-bit in sync
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opening as "WIP", to make CI run here (bumping / regenerating caused some issues when I did the same in the swarmkit repository)