-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor UnboundOpExecutionContext.bind to use contextmanager #15990
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
5101150
to
47aa075
Compare
410c461
to
7efef15
Compare
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 4f9a917. |
7efef15
to
cb8062b
Compare
cb8062b
to
8bc7365
Compare
Deploy preview for dagit-storybook ready! ✅ Preview Built with commit 4f9a917. |
1de6541
to
de8a156
Compare
8bf6075
to
d03c862
Compare
d03c862
to
4f9a917
Compare
Summary & Motivation
UnboundOpExecutionContext.bind current uses the exit stack to manage contextful resources created for a single call. This unnecessarly couples it to that instance. Instead we can just use the native contextmanager facility, which ends up being more composable.
How I Tested These Changes
BK