Skip to content
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

Virtual context improvements #5384

Merged
merged 2 commits into from
Nov 6, 2024
Merged

Virtual context improvements #5384

merged 2 commits into from
Nov 6, 2024

Conversation

vietj
Copy link
Member

@vietj vietj commented Nov 5, 2024

No description provided.

@vietj vietj added this to the 5.0.0 milestone Nov 5, 2024
…utor is closed.

Motivation:

Future.await incorrectly performs a no-op when the worker executor is closed (returns a null latch), which reports a failure that might not exist.

Changes:

When the worker executor returns null, throw an interrupted exception.
Motivation:

Context#close implementation is currently too drastic and will refuse to execute any task in addition of interrupting threads. After a context is closed there is often the need to let task execution happen in order to cleanup state, e.g. pending HTTP tasks due to back-pressure catch up or timers.

Changes:

Context#close now allows to execute tasks.
@vietj vietj force-pushed the virtual-context-improvements branch from da1b321 to ee8fe79 Compare November 5, 2024 09:23
@vietj vietj merged commit 8b9a3e5 into master Nov 6, 2024
8 checks passed
@vietj vietj deleted the virtual-context-improvements branch November 6, 2024 07:43
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.

1 participant