Repository navigation
fix(judge): forward the configured ensemble endpoint - #207
Merged
n-papaioannou merged 2 commits intoOct 6, 2026
Merged
n-papaioannou merged 2 commits into
n-papaioannou merged 2 commits into
Conversation
Signed-off-by: Rudy Celekli <47457359+rudycelekli@users.noreply.github.com>
rudycelekli
requested review from
Sebabaian,
dimneo,
n-papaioannou and
stefyi-4355
as code owners
October 6, 2026 11:09
n-papaioannou
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EnsembleJudgeEvaluator drops the public JudgeConfig.endpoint while constructing its members. A native B19 run sends both judges to the owned default server and fails despite a passing configured server. Forward the parent endpoint to each member. The no-endpoint default route remains covered.
Validation
Worked example
Actual synthetic native scorecard fields (plumbing verification, not a live model assessment):
[ { "case": "test_public_ensemble_uses_conf0", "custom_endpoint": true, "calls": { "configured": { "sut": 60, "first": 30, "second": 30 }, "default": {} }, "test_id": "B19", "score": 1.0, "status": "pass" }, { "case": "test_public_ensemble_uses_conf1", "custom_endpoint": false, "calls": { "configured": { "sut": 60 }, "default": { "first": 30, "second": 30 } }, "test_id": "B19", "score": 1.0, "status": "pass" } ]The public ensemble configuration has a shared endpoint; per-member endpoint overrides are not introduced. Three advisory ensemble-stat typing errors predate this change.
Prepared with AI assistance and reviewed before publication.
Exact-head CI
All three unchanged fork CI jobs (Python 3.10/3.11/3.12) passed at signed+DCO head
77ad1296a96fea10add7922fbd5d3a63a6d77b17: workflow evidence. These jobs run installation, lint, Bandit, layout and fixture validation; the native pytest results above were run locally. Upstream CI isaction_requiredpending maintainer authorization; maintainer review remains separate.