Skip to content

[eval] Optionnally use the gateway for the llm as a judge#2092

Merged
dgageot merged 1 commit intodocker:mainfrom
dgageot:llm-judge-gateway
Mar 12, 2026
Merged

[eval] Optionnally use the gateway for the llm as a judge#2092
dgageot merged 1 commit intodocker:mainfrom
dgageot:llm-judge-gateway

Conversation

@dgageot
Copy link
Member

@dgageot dgageot commented Mar 12, 2026

No description provided.

Signed-off-by: David Gageot <david.gageot@docker.com>
@dgageot dgageot requested a review from a team as a code owner March 12, 2026 16:00
@dgageot dgageot changed the title Optionnally use the gateway for the llm as a judge [eval] Optionnally use the gateway for the llm as a judge Mar 12, 2026
Copy link

@docker-agent docker-agent bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Summary

Assessment: 🟢 APPROVE

Summary

This PR adds optional gateway support for the LLM judge by conditionally configuring the WithGateway option when ModelsGateway is set. The implementation is clean and follows the existing pattern already established in eval.go:createJudgeModel.

Key observations:

  • ✅ Options slice is properly initialized with WithStructuredOutput
  • ✅ Gateway option is conditionally appended only when ModelsGateway is non-empty
  • ✅ Options are correctly passed as variadic arguments to provider.New
  • ✅ Follows the identical pattern used elsewhere in the codebase (eval.go lines 745-748)
  • ✅ No race conditions, resource leaks, or error handling issues introduced

Findings

No bugs found in the changed code. The implementation is correct and ready to merge.

@dgageot dgageot merged commit 13054f4 into docker:main Mar 12, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants