You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d61e7a7
Browse filesBrowse the repository at this point in the historyBrowse files
feat(gooddata-eval): extend detail.latency_breakdown to 5 remaining kinds
latency_breakdown (#1758) was wired into only the 9 test kinds the downstream
consumer had enabled, not the SDK's full kind catalog. This closes the gap for
metric_skill, alert_skill, agentic_search, agentic_general_question and
agentic_kda_skill -- all of which already receive real tool_call_events/
reasoning_step_events through the same chat pipeline as their wired siblings.
dashboard_summary is deliberately excluded: it calls a plain REST /summary
endpoint, not the chat/SSE pipeline, so it has no tool-call or reasoning-step
events to report at all.
Also extracts the per-turn timestamp/index rebasing -- previously hand-copied
identically across alert_skill, metric_skill, visualization and conversation,
and needed a fifth time for agentic_kda_skill's simulated-user loop -- into one
shared shift_and_index_events() in models.py. All five call sites use it, so
there is one implementation rather than five that can drift.
Tests: a two-iteration kda test asserts the real rebasing math (iteration 2's
call_ts shifted by iteration 1's turn_wall_clock_sec, tool index from 0 while
reasoning index starts from 1), plus per-run event-propagation guards for
search_tool (which still builds its result in two places) and general_question.
Rebased onto #1771, which restructured the same K-run loops: general_question
now builds all K runs and one shared detail dict in a single place, so the
propagation fix collapses to one site there; search_tool still has two.
0 commit comments