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 316a0dc
Browse filesBrowse the repository at this point in the historyBrowse files
Merge branch 'master' into integration/eval-rebuild
Master gained #1847 (user_context on every kind), #1849 (adhoc-visualization
fallback logging, metric-delete recheck, chart-execution reporting) and
#1852 (W3C baggage trace labels).
Resolutions:
- cli/agentic_runner.py: additive imports on both sides, then one duplicate
`user_context=item.user_context` removed -- both sides had added it to the
report-skill branch independently.
- core/agentic/visualization.py: #1849 added two lines to the assertion
message (Executed, Stated Value Matches) exactly where this branch moved
the raise behind the shared outcome tail. Both land.
- tests/test_agentic_general_question.py: #1847 relocated the local
user_context test into its own cross-kind table, so its deletion stands;
this branch's per-run failure assertions beside it stay.
- tests/test_agentic_runner.py rebuilt from master's copy plus the fourteen
blocks that exist only here. A union is wrong for this file: one hunk
begins mid-test, with its head on the other side.
The two branch-only kinds were re-added to master's coverage tables:
dashboard_summary and forecasting are absent from any table written against
master. dashboard_summary stays OUT of the user-context relay, with the
reason recorded -- it builds its own context from the dashboard it
summarises and takes its scope from summary_input.
1754 passed, 2 skipped. ruff clean.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|`GOODDATA_EVAL_CHAT_*`| SSE retry, backoff and timeout knobs |
159
+
|`GOODDATA_EVAL_TRACE_LABELS`|`key=value,...` labels stamped on every observation of a chat conversation via W3C baggage; `model_version` also sets the observation `version`, so set it only for a one-model run: every `--model` in one process gets the same labels. Keys must match `[A-Za-z0-9_-]+`; others are skipped with a warning. Dashboard-summary runs are not labelled |
159
160
|`GD_EVAL_TIMERS`| same as `--timers`|
160
161
161
162
A gitignored `.env` at the repo root is the normal place for these; load it with
0 commit comments