-
Notifications
You must be signed in to change notification settings - Fork 623
buildflags: handle unknown values from cty #2965
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| module github.com/docker/buildx | ||
|
|
||
| go 1.22.0 | ||
| go 1.23.0 | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Was this intentional; i.e., go1.22 no longer supported with this change?
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was intentional to be able to use I've opened #2978 to keep the bones of this functionality but to revert the compiler usage of the feature. |
||
|
|
||
| require ( | ||
| github.com/Masterminds/semver/v3 v3.2.1 | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
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.
Was looking at how this example behaves in Buildx 0.19 and I got 13 diagnostics:
But here I got 8 diagnostics:
Not for this PR but wonder if we could show all diags when
--debugis set?nit: Also seems to return OUTPUT as first diag with this PR but in older release returns what seems to be the first one FOO1
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.
I'd definitely say we should show all diagnostics. The number of diagnostics can be a bit strange sometimes because they will sometimes depend on the ordering of evaluation and one diagnostic can trigger another diagnostic. There will also be some diagnostics sometimes that say "cannot use unknown value" that are triggered somewhere.