fix: capture agent end_time before emitting agent_stats - #9597
Merged
Conversation
wcqqq1214
marked this pull request as ready for review
August 8, 2026 03:48
Soulter
approved these changes
Aug 8, 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.
Modifications / 改动点
In
tool_loop_agent_runner.py, captureend_timeright before theagent_statssnapshot is serialized viato_dict(). Previouslyend_timewas only set after the yield (inside_complete_with_assistant_response), so the frontend receivedend_time=0and the per-message elapsed duration (耗时) in the webchat detail panel always displayed as "-". Token counts and time-to-first-token were unaffected.This is NOT a breaking change. / 这不是一个破坏性变更。
Verification Steps / 验证步骤
Screenshots or Test Results / 运行截图或测试结果
Before / 修复前
After / 修复后
Checklist / 检查清单
😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
/ 如果 PR 中有新加入的功能,已经通过 Issue / 邮件等方式和作者讨论过。(本 PR 无新功能)
👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
/ 我的更改经过了良好的测试,并已在上方提供了"验证步骤"和"运行截图"。(截图待补充)
🤓 I have ensured that no new dependencies are introduced.
/ 我确保没有引入新依赖库。
😮 My changes do not introduce malicious code.
/ 我的更改没有引入恶意代码。
Summary by Sourcery
Bug Fixes:
Summary by Sourcery
Bug Fixes: