fix: wait for peer ACK in notify and notify_0rtt before returning
#87
+14
−3
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.
Suggestion cannot be applied right now. Please check back later.
Without this, the QUIC CONNECTION_CLOSE frame sent when the caller closes the connection can race with (and arrive before) the stream data at the server, causing the server's accept_bi to see ApplicationClosed instead of the notify message.
Call finish() to signal end-of-stream, then stopped().await to wait for the peer's transport-level ACK before returning. This ensures the server has the stream data before the connection is closed.