Skip to content

Fix NetSocket (and QuicStream) where the end signal is notified before all messages have been dispatched.#5968

Merged
vietj merged 1 commit intomasterfrom
fix-out-of-order-socket-end-message
Feb 12, 2026
Merged

Fix NetSocket (and QuicStream) where the end signal is notified before all messages have been dispatched.#5968
vietj merged 1 commit intomasterfrom
fix-out-of-order-socket-end-message

Conversation

@vietj
Copy link
Member

@vietj vietj commented Feb 12, 2026

Motivation:

The NetSocket implementation directly write the end sentinel message to the pending message queue, ignoging the potentially buffered messages in the connection.

Changes:

When we consider the message stream ends, we should instead model the last message as a connection message to ensure no reorder happens.

@vietj vietj added this to the 5.1.0 milestone Feb 12, 2026
@vietj vietj force-pushed the fix-out-of-order-socket-end-message branch from 36761b6 to 12f2775 Compare February 12, 2026 15:41
…e all messages have been dispatched.

Motivation:

The NetSocket implementation directly write the end sentinel message to the pending message queue, ignoging the potentially buffered messages in the connection.

Changes:

When we consider the message stream ends, we should instead model the last message as a connection message to ensure no reorder happens.
@vietj vietj force-pushed the fix-out-of-order-socket-end-message branch from 12f2775 to 67e301e Compare February 12, 2026 15:47
@vietj vietj added the bug label Feb 12, 2026
@vietj vietj self-assigned this Feb 12, 2026
@vietj vietj merged commit 4350abd into master Feb 12, 2026
15 of 19 checks passed
@vietj vietj deleted the fix-out-of-order-socket-end-message branch February 12, 2026 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant