Introduce async DrainStrategy, DrainAction, Observer, and Call types#1364
Merged
Merged
Conversation
Collaborator
Author
|
Test issue is unrelated, see: #1365 for the fix. |
TristonianJones
force-pushed
the
async-helpers
branch
from
July 15, 2026 20:09
6509b3d to
cdeaa8e
Compare
jnthntatum
approved these changes
Jul 16, 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
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.
Create
cel/asyncpackage with interfaces used by concurrent evalasync.Callis a read-only view of a pending or completed async operationasync.Observercan be used to receive start / stop notification for anasync.Callasync.DrainStrategycontrols how and when to consume async call results in an evaluationasync.DrainActionindicates how the concurrent evaluation should treat the batch of resultsConcurrentEvalwill initiate a CEL expression evaluation that triggers one or more asynccalls. As calls complete, the expression evaluation will be performed again using the results
from the call to advance the expression evaluation to a conclusive state.