Fix Agent_message does not load runIds anymore #6248
Merged
Conversation
This file contains 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
fontanierh
approved these changes
Jul 16, 2024
albandum
pushed a commit
that referenced
this pull request
Aug 28, 2024
* Fix Agent_message does not load runIds anymore * Attach runIds directly to agent_message_success
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.
Description
Task: https://github.com/dust-tt/tasks/issues/1061
Event
agent_generation_successwas in charge of setting the runIds.We've stop yielding this event here: https://github.com/dust-tt/dust/pull/6169/files to use instead
agent_message_successThis PR edits
agent_message_successto attach the runId and be able to retrieve them and attach them to the agentMessage.Risk
Will test on front-edge.
Can be rolled back.
Deploy Plan
Deploy front.