-
Notifications
You must be signed in to change notification settings - Fork 1k
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
go 1.21 support #2456
Comments
The current development code is completely broken, so this is not a good candidate for a release. I can try to revert the changes that broke the cache updates, see if a release can be made before reintroducing them and eventually understanding how they can be fixed. |
Thanks for letting me know the status. fwiw building against 5085a22 worked with go 1.21 / quic-go and dnscrypt-proxy itself runs. |
CI doesn't pass. There's another issue which is hard to find because it was a comment on a commit, but it's also a blocker. |
Version 2.1.5 released! |
Reported bugs must reproducible in the context described in the "Context" section.
Installation and configuration issues are not bugs, but individual assistance request.
Context: the LATEST version of
dnscrypt-proxy
(precompiled binaries downloaded from this repository) is correctly installed and configured on your system, but something doesn't seem to produce the expected result.If the bug is not trivial to reproduce on any platform, please include ALL the steps required to reliably duplicate it, on a vanilla, generic install of macOS, Windows, OpenBSD or Ubuntu Linux system, in their most current version.
If you don't have any clear understanding of the issue or can't enumerate the steps to reproduce it, open a discussion instead:
https://github.com/DNSCrypt/dnscrypt-proxy/discussions
Output of the following commands:
./dnscrypt-proxy -version
./dnscrypt-proxy -check
./dnscrypt-proxy -resolve example.com
What is affected by this bug?
using go 1.21 causes build breakage with latest dnscrypt-proxy release
When does this occur?
trying to build from openbsd ports which has recently updated go to 1.21
Where does it happen?
build breakage
How do we replicate the issue?
Expected behavior (i.e. solution)
successfully build against go 1.21
Other Comments
what is the status of go 1.21 support? can a new release be made supporting go 1.21 and quic-go? I see the recent commits supporting these: 0a98be9 and 0a98be9
I'm trying to update the openbsd port and would want to update to a new release if available.
The text was updated successfully, but these errors were encountered: