Skip to content

Propagate cancellation tokens through monitoring hosting and background services - #5751

Merged
johnsimons merged 1 commit into
masterfrom
john/cancel_phase6
Aug 13, 2026
Merged

Propagate cancellation tokens through monitoring hosting and background services#5751
johnsimons merged 1 commit into
masterfrom
john/cancel_phase6

Conversation

@johnsimons

Copy link
Copy Markdown
Member

This change continues the effort to consistently apply optional CancellationToken parameters to asynchronous methods across the monitoring project, including hosting commands, background services, and acceptance test infrastructure.

Cancellation tokens are now propagated to underlying asynchronous operations, ensuring proper responsiveness to cancellation and retiring the remaining cancellation analyzer debt for the monitoring projects.

@johnsimons
johnsimons requested a review from rbev August 12, 2026 05:28
@johnsimons johnsimons self-assigned this Aug 12, 2026
Base automatically changed from john/cancel_transports to master August 12, 2026 08:13
…nd services

This change continues the effort to consistently apply optional `CancellationToken` parameters to asynchronous methods across the monitoring project, including hosting commands, background services, and acceptance test infrastructure.

Cancellation tokens are now propagated to underlying asynchronous operations, ensuring proper responsiveness to cancellation and retiring the remaining cancellation analyzer debt for the monitoring projects.
@johnsimons
johnsimons merged commit 27033c9 into master Aug 13, 2026
105 of 106 checks passed
@johnsimons
johnsimons deleted the john/cancel_phase6 branch August 13, 2026 03:40
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