ngtcp2: use 0.15.0 #11031
Closed
ngtcp2: use 0.15.0 #11031
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We can't upgrade yet, because we need nghttpx and it is a part of nghttp2 and it still uses the deprecated ngtcp2 APIs even in current git master so it fails to build. |
|
nghttp2 v1.52 cannot be built with ngtcp2 v1.15. Please wait for nghttp2 v1.53 to upgrade. |
|
@tatsuhiro-t any chance there is a nghttp2 release pending? We just ran into #11090 that seems to not happen on the latest ngtcp2 version, so we would like to take the jump... |
|
I will make new nghttp2 release tomorrow. I'm not sure the bug mentioned in #11090 has been fixed in the latest ngtcp2 release and main. Will check. |
|
Is there a rebase planned here? |
Adapt to new API calls
bagder
force-pushed
the
bagder/bump-ngtcp2
branch
from
20a1851
to
b5873bc
Compare
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Adapt to new API calls