-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
feat: implement follow-up message handling in ToolLoopAgentRunner #5484
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这里存在一个竞态条件。
_pending_follow_ups列表会在没有同步机制的情况下被多个协程访问。follow_up方法(从一个协程调用)会向列表追加内容,而_consume_follow_up_notice和_resolve_unconsumed_follow_ups等方法(从代理的step协程调用)会读取并清空它。这可能导致后续消息丢失。为了修复这个问题,建议使用
asyncio.Lock来保护对self._pending_follow_ups的所有访问。self._follow_up_lock = asyncio.Lock()。follow_up,_resolve_unconsumed_follow_ups, 和_consume_follow_up_notice方法改为async。_pending_follow_ups的临界区代码包裹在async with self._follow_up_lock:中。await。例如,_merge_follow_up_notice也需要变成async。