Skip to content

Conversation

@mtmk
Copy link
Member

@mtmk mtmk commented Jul 29, 2025

The idea is to avoid exceptions killing the pull loop and rely on timeouts to retry the pull in worst case scenario.

Copy link
Contributor

@scottf scottf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mtmk mtmk merged commit 0d77cc4 into main Jul 31, 2025
22 checks passed
@mtmk mtmk deleted the fix-consumer-pull-loop-error-handling branch July 31, 2025 15:31
mtmk added a commit that referenced this pull request Aug 1, 2025
* Add watcher cancellation handling (#881)
* Fix pull request exception handling (#919)
* Add RequestTimeout option to NatsJSOpts for request operations (#918)
@mtmk mtmk mentioned this pull request Aug 1, 2025
mtmk added a commit that referenced this pull request Aug 1, 2025
* Add watcher cancellation handling (#881)
* Fix pull request exception handling (#919)
* Add RequestTimeout option to NatsJSOpts for request operations (#918)
@mtmk mtmk mentioned this pull request Sep 22, 2025
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.

Broken PullLoop inside NatsJsConsume in case of an exception at CallNextMsgAsync

3 participants