Use context.WithoutCancel instead of context.Background#8635
Merged
beautifulentropy merged 4 commits intomainfrom Feb 23, 2026
Merged
Use context.WithoutCancel instead of context.Background#8635beautifulentropy merged 4 commits intomainfrom
beautifulentropy merged 4 commits intomainfrom
Conversation
jsha
reviewed
Feb 20, 2026
jsha
approved these changes
Feb 23, 2026
beautifulentropy
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I found a few places where we were using context.Background(), but actually had a perfectly good parent context to inherit from available. Fix those to better match best practices, and propagate the parent context's other metadata deeper into the call stack.