Skip to content

Conversation

@ejona86
Copy link
Member

@ejona86 ejona86 commented Jul 17, 2025

In observed cases, whether RST_STREAM or another failure from netty or the server, listeners can fail to be notified when a connection yields a null stream for the selected streamId. This causes hangs in clients, despite deadlines, with no obvious resolution.

This is not simply a race between netty to deliver a result interpreted as a failure and the setSuccess previously implemented, the netty layer does not report the stream as failed.

Fixes #12185

Backport of #12207

In observed cases, whether RST_STREAM or another failure from netty or
the server, listeners can fail to be notified when a connection yields a
null stream for the selected streamId. This causes hangs in clients,
despite deadlines, with no obvious resolution.

Tests which relied upon this promise succeeding must now change.
@ejona86 ejona86 requested a review from kannanjgithub July 17, 2025 22:01
@ejona86 ejona86 merged commit b04c673 into grpc:v1.74.x Jul 18, 2025
16 checks passed
@ejona86 ejona86 deleted the backport-null-stream-promise-1.74 branch July 18, 2025 16:05
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants