-
Notifications
You must be signed in to change notification settings - Fork 955
Compiling 2021.8.3 using Go 1.17 fails #442
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
Comments
This only requires updating quic-go to the latest version. Line 32 in 4ff215e
It's already been fixed in Caddy. caddyserver/caddy#4297 |
Looks like @sudarshan-reddy downgraded quic-go to 0.20.0 a few days ago in 1082ac1 quic-go did fix the panic in 0.21.2 which is newer than what the commit downgraded from (0.21.1) |
Yes, we've had to downgrade to avoid pulling golang/go#43989 back in. In the meantime, out of curiosity, what's driving you to compile the repo on every release? |
@nmldiegues Mostly as a way of learning to build minimal multi-platform images for things that I use as well as GitHub Actions. After a bunch of trials, I think I figured out a fairly clean way to build images (in particular, go based apps) to the point where I can containerize a Go binary in about 15-20 mins. Feel free to take a look at https://github.com/jauderho/dockerfiles or #422 (comment) (for details around specifically around how I build cloudflared) |
I'm actively working on this upgrade and syncing it with our build system. I'll keep you guys posted. |
This is now fixed.
|
This was working with no errors for 2021.8.2.
The error message is https://github.com/jauderho/dockerfiles/runs/3419574175?check_suite_focus=true#step:8:2063
Seems to be a known issue as caddyserver is reporting similar issues. See caddyserver/caddy#4118
For now, I've reverted to building with Go 1.16.
The text was updated successfully, but these errors were encountered: