[futures] provide context propagation for concurrent module
#429
Conversation
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
palazzem
force-pushed
the
palazzem/futures-integration
branch
2 times, most recently
from
2c17fa6 to
2090937
Compare
palazzem
force-pushed
the
palazzem/futures-integration
branch
from
2090937 to
9bf5677
Compare
…o uses the `futures` integration
palazzem
force-pushed
the
palazzem/futures-integration
branch
from
9bf5677 to
5431f88
Compare
LotharSee
approved these changes
Mar 5, 2018
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.
Overview
Makes the
futuresTornado context propagation globally available, as a standalone integration. The new integration is not enabled by default and requirespatch(futures=True)orpatch_all(futures=True).This integration does only context propagation between threads of the same
ThreadPoolExecutor, and does not create, nor trace the thread execution.