Skip to content
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

Update quic-go for Go 1.21 support #183

Closed
wants to merge 1 commit into from
Closed

Update quic-go for Go 1.21 support #183

wants to merge 1 commit into from

Conversation

anacrolix
Copy link
Contributor

This blocks updating quic-go for flashlight and friends.

This blocks updating quic-go for flashlight and friends.
@myleshorton
Copy link
Contributor

This overlaps with the changes here, but I think most importantly we can't just update quic here vs in quicwrapper if the goal is to upgrade quic on the client side...and that has to be tested to make sure it's actually compatible with http-proxy-lantern because we use our fork with things like BBR and performance metrics.

@noahlevenson
Copy link
Contributor

I don't understand the full context of what's going on here. In particular, I don't understand what this means:

we can't just update quic here vs in quicwrapper if the goal is to upgrade quic on the client side

Is it very important for me to learn this stuff and figure this out now, or can it wait a little while?

My preference would be to put this on ice for a moment as we head into the beta. But if it's blocking some very important stuff I can dig into it?

@myleshorton
Copy link
Contributor

Putting it on ice is fine. I think the intent is to allow us to update to the latest Go, but this is the least of our worries for that goal.

@noahlevenson
Copy link
Contributor

This ultimately was addressed here: #207

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants