Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Evaluation: Improve guardrails awareness

Aperta
  • Qualcosa non va?
#1,246 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@AkhileshNegi ci sta già lavorando.

Dal 28/9/2026.

  • #1208 di @AkhileshNegi — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
fastapi, python
Ambito
ai, backend-api-design

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
18
Fork
11
Merge medio
3g 11h
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ProjectTech4DevAI/kaapi-backend

Tutte le issue di ProjectTech4DevAI/kaapi-backend

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.