Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Evaluation: Improve guardrails awareness

已关闭
  • 哪里不对？
#1,246 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@AkhileshNegi 已经在做这个了。

开始于 2026年9月28日。

  • #1208 来自 @AkhileshNegi —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
停滞
技术栈
fastapi, python
领域
ai, backend-api-design

调研方向

The issue says the evaluation job's v2 path and GET /api/v1/evaluations/{id} results are involved; start by tracing that evaluation path and the execute_llm_call path. Check how guardrail data passes through retries, merging, scoring, and traces. Done means fast/v2 evaluations apply input and output guardrails and expose the requested per-row fields without recording eval traffic as llm_call rows; the issue reports this work as implemented in #1208.

由索引模型根据 Issue 内容生成。

描述

enhancement

Is your feature request related to a problem?
Text evaluations (fast run mode / v2) currently ignore the stored input and output guardrails. This leads to eval scores that don't accurately reflect the system's behavior in production.

Describe the solution you'd like

  • Make fast/v2 evaluations guardrails-aware: check each dataset query against input_guardrails before the LLM call and the response against output_guardrails after.
  • Use the execute_llm_call path instead of a separate eval-only path, avoiding the recording of eval traffic as llm_call rows.
  • Include per-row guardrail status, input_to_llm, and output_from_llm in GET /api/v1/evaluations/{id} results.
  • Carry guardrail data through retry, merge, scoring, and traces.
Original issue

Is your feature request related to a problem?
Text evaluations (fast run mode / v2) ignore the input and output guardrails stored on the config. The golden dataset query is sent straight to the LLM and the generated response is never checked by output guardrails, so eval scores don't reflect how the config actually behaves in production via /llm/call.

Describe the solution you'd like

  • Make the fast/v2 evaluation run guardrails-aware: run each dataset query through the config's input_guardrails before the LLM call, and the response through output_guardrails after.
  • Reuse the execute_llm_call path instead of a separate eval-only LLM path, without recording eval traffic as llm_call rows / production metrics.
  • Surface per-row guardrail status, input_to_llm and output_from_llm in GET /api/v1/evaluations/{id} results.
  • Carry guardrail data through retry, merge, scoring and traces.

Original issue

Earlier doing text evals v2 used not to take into account the stored input and output validators ids and instead sending the input / output straight to openAI. Now the evaluation job (v2) is guardrails aware; meaning the query in the golden dataset is passed through input guardrails if they are stored; similar functionality for responses generated (if o/p guardrails are configured).

Comments: Implemented in #1208.

主要语言
Python
星标
18
派生
11
平均合并
4 天 16 小时
30 天内合并 PR
11

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

ProjectTech4DevAI/kaapi-backend 的其他 Issue

查看 ProjectTech4DevAI/kaapi-backend 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。