-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
containerd module causes an EmbeddedAliasFields panic #827
Labels
bug
Something isn't working
Comments
We will solve this class of bugs entirely when we can start using alias tracking in Go 1.22/1.23 per golang/go#63223 and golang/go#64208. I tried giving the early support in Go 1.22 a try, but I ran into a panic (golang/go#65778), so I think it's too early. |
This will be finally resolved once golang/go#70517 is released by Go. |
mvdan
added a commit
to mvdan/garble-fork
that referenced
this issue
Jan 16, 2025
Allows us to remove EmbeddedAliasFields, recordedObjectString, and all the logic around using them. Resolves an issue where a user was running into a panic in our logic to record embedded aliases. Fixes burrowers#827.
mvdan
added a commit
to mvdan/garble-fork
that referenced
this issue
Jan 17, 2025
Allows us to remove EmbeddedAliasFields, recordedObjectString, and all the logic around using them. Resolves an issue where a user was running into a panic in our logic to record embedded aliases. Note that this means we require Go 1.23.5 or later now, which also meant some changes to goversion.txtar to keep it green. Fixes burrowers#827.
lu4p
pushed a commit
that referenced
this issue
Jan 18, 2025
Allows us to remove EmbeddedAliasFields, recordedObjectString, and all the logic around using them. Resolves an issue where a user was running into a panic in our logic to record embedded aliases. Note that this means we require Go 1.23.5 or later now, which also meant some changes to goversion.txtar to keep it green. Fixes #827.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Garble and Go are you using?
What environment are you running Garble on?
go env
OutputWhat did you do?
I tried building my project with garble
What did you expect to see?
Build going through and go binary
What did you see instead?
error pointing to containerd package
build output
The text was updated successfully, but these errors were encountered: