Skip to content

Propagate cancellation tokens through group data store persistence - #5737

Merged
johnsimons merged 1 commit into
john/cancel_part6from
john/cancel_part7
Aug 12, 2026
Merged

johnsimons merged 1 commit into
john/cancel_part6from
john/cancel_part7

Conversation

@johnsimons

Copy link
Copy Markdown
Member

This change continues the effort to consistently apply optional CancellationToken parameters to asynchronous methods within the IGroupsDataStore interface, its EFCore and RavenDB implementations, and related consuming services.

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

@johnsimons johnsimons self-assigned this Aug 11, 2026
@johnsimons
johnsimons requested a review from rbev August 11, 2026 10:53
@johnsimons
johnsimons marked this pull request as ready for review August 11, 2026 10:53
This change continues the effort to consistently apply optional `CancellationToken` parameters to asynchronous methods within the `IGroupsDataStore` interface, its EFCore and RavenDB implementations, and related consuming services.

Cancellation tokens are now propagated to underlying asynchronous database calls, ensuring proper cancellation of long-running operations and further reducing cancellation analyzer debt.
@johnsimons
johnsimons merged commit 7b76ce5 into master Aug 12, 2026
50 checks passed
@johnsimons
johnsimons deleted the john/cancel_part7 branch August 12, 2026 02:53
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