fix: Preserve contextvars in aiohttp integration#674
Merged
untitaker merged 1 commit intogetsentry:masterfrom Apr 20, 2020
H--o-l:fix/contextvars-aiohttp-exception
Merged
fix: Preserve contextvars in aiohttp integration#674untitaker merged 1 commit intogetsentry:masterfrom H--o-l:fix/contextvars-aiohttp-exception
untitaker merged 1 commit intogetsentry:masterfrom
H--o-l:fix/contextvars-aiohttp-exception
Conversation
Member
|
You can inline |
aiohttp integration currently re-create a task to encapsulate the request handler. But: - aiohttp already does it. - contextvars created in it can't be read by aiohttp. It's an issue for users custom logger. Fix #670
Contributor
Author
|
@untitaker Ok, something like what I just push? |
Member
|
Perfect, thanks! |
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
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.
aiohttp integration currently re-create a task to encapsulate the request
handler.
But:
It's an issue for users custom logger.
Fix #670