Skip to content

fix: continue when receiver has lagged messages and log event#1374

Merged
gilcu3 merged 2 commits intomainfrom
1359-ckdrequeststorageget-treats-any-broadcast-receive-error-as-fatal
Nov 4, 2025
Merged

fix: continue when receiver has lagged messages and log event#1374
gilcu3 merged 2 commits intomainfrom
1359-ckdrequeststorageget-treats-any-broadcast-receive-error-as-fatal

Conversation

@gilcu3
Copy link
Copy Markdown
Contributor

@gilcu3 gilcu3 commented Nov 4, 2025

Closes #1359

@gilcu3 gilcu3 linked an issue Nov 4, 2025 that may be closed by this pull request
…eget-treats-any-broadcast-receive-error-as-fatal
@gilcu3 gilcu3 enabled auto-merge November 4, 2025 14:24
@gilcu3 gilcu3 added this pull request to the merge queue Nov 4, 2025
Merged via the queue into main with commit b5be008 Nov 4, 2025
11 checks passed
@gilcu3 gilcu3 deleted the 1359-ckdrequeststorageget-treats-any-broadcast-receive-error-as-fatal branch November 4, 2025 14:59
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.

CKDRequestStorage::get treats any broadcast receive error as fatal

2 participants