Skip to content

Propagate cancellation tokens through failed message editing and notification persistence - #5743

Merged
johnsimons merged 1 commit into
john/cancel_part10from
john/cancel_part11
Aug 12, 2026
Merged

johnsimons merged 1 commit into
john/cancel_part10from
john/cancel_part11

Conversation

@johnsimons

@johnsimons johnsimons commented Aug 11, 2026 •

Copy link
Copy Markdown
Member

This change continues the effort to consistently apply optional CancellationToken parameters to asynchronous methods within the IEditFailedMessagesDataStore, INotificationsDataStore, and related manager interfaces, along with their EFCore and RavenDB implementations.

Cancellation tokens are now propagated to underlying asynchronous database calls, ensuring proper cancellation of long-running operations.

@johnsimons
johnsimons requested a review from rbev August 11, 2026 23:19
@johnsimons johnsimons self-assigned this Aug 11, 2026
…fication persistence

This change continues the effort to consistently apply optional `CancellationToken` parameters to asynchronous methods within the `IEditFailedMessagesDataStore`, `INotificationsDataStore`, and related manager interfaces, along with their EFCore and RavenDB implementations.

Cancellation tokens are now propagated to underlying asynchronous database calls, ensuring proper cancellation of long-running operations.
@johnsimons
johnsimons merged commit 0f813d9 into master Aug 12, 2026
50 checks passed
@johnsimons
johnsimons deleted the john/cancel_part11 branch August 12, 2026 04:07
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.

2 participants