Repository navigation
Conversation
…apter In some variants of a durable setup, it's impossible to prevent tool results for tools that have been aborted due to a llm retry from showing up in the workflow stream *after* the Retry event does. Downstream users will need to deal with this. Add a RetryFilter class for dealing with it and also update the ui adapter to use it. MessageHydrator and other things use it internally to make their logic work better but don't filter the events. Maybe we want to expose a more ergonomic adapater also, I'm not sure?
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
In some variants of a durable setup, it's impossible to prevent tool
results for tools that have been aborted due to a llm retry from
showing up in the workflow stream after the Retry event does.
Downstream users will need to deal with this.
Add a RetryFilter class for dealing with it and also update the ui
adapter to use it. MessageHydrator and other things use it
internally to make their logic work better but don't filter the
events.
Maybe we want to expose a more ergonomic adapater also, I'm not sure?