-
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
Make QUIC The Default Transport #14688
Conversation
This would be a good time to update quic-go to the latest. It has been a while since we updated it. |
352fe60
to
6fb00f5
Compare
e5c4063
to
fe88018
Compare
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 reviewed libp2p updates and LGTM
(Reviewed them as well!) |
Hey folks. Just making a note that this could be breaking someones setup if they used the |
…he new quic port (#845) Prysm added QUIC to their client as per prysmaticlabs/prysm#14688 . This currently broke our runs using the master branch prysm image due to the QUIC port running on 13000 by default. Which was conflicting with the settings we were providing for the UDP port: ```sh --p2p-quic-port value The QUIC port used by libp2p. (default: 13000) --p2p-tcp-port value The TCP port used by libp2p. (default: 13000) --p2p-udp-port value The UDP port used by the discovery service discv5. (default: 12000) ``` I've also added the CLI flags for it, but still commented out until a stable release is done.
Thanks for bringing this up @skylenet, that is a good point. We will add this to our release notes to flag that this port will be taken up. |
What type of PR is this?
Feature
What does this PR do? Why is it needed?
This makes
QUIC
the default transport protocol in prysm and will make every prysm node connect to other nodes via QUIC if supported.Which issues(s) does this PR fix?
N.A
Other notes for review
Acknowledgements