Skip to content

fix(gsoc): sequential messaging - #5593

Open
nugaon wants to merge 2 commits into
masterfrom
fix/gsoc-sequential
Open

fix(gsoc): sequential messaging#5593
nugaon wants to merge 2 commits into
masterfrom
fix/gsoc-sequential

Conversation

@nugaon

@nugaon nugaon commented Sep 2, 2026

Copy link
Copy Markdown
Member

addressing #5497 (comment)

@nugaon nugaon mentioned this pull request Sep 2, 2026
6 tasks
gsoc.Handle spawned a goroutine per subscriber handler, so message
delivery order to a subscriber was not guaranteed. Call handlers
synchronously in registration order instead.
@nugaon
nugaon force-pushed the fix/gsoc-sequential branch from 125e62e to b15df1b Compare September 2, 2026 15:19
@akrem-chabchoub

Copy link
Copy Markdown
Contributor

dataC's buffer of 2 was too small for a legitimate burst of GSOC
messages delivered concurrently to the same subscriber (e.g. several
chunks pushed at once), causing a false-positive slow-consumer
disconnect. Bump it to 16 and adjust the slow-consumer test's message
count so overflow is still hit deterministically.
@nugaon

nugaon commented Sep 2, 2026

Copy link
Copy Markdown
Member Author

Thanks for flagging — the ordering fix wasn't the full story. The remaining flakiness in the "parallel" ci-gsoc case (10 messages delivered concurrently to one subscriber) was a false-positive "slow consumer" disconnect: the websocket delivery channel only buffered 2 messages, so a legitimate burst tripped the overflow check meant for genuinely stuck clients. Bumped the buffer to 16 in 0be4122 (TestGsocWebsocketSlowConsumer adjusted to still hit real overflow deterministically). Let's see if CI is green now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants