Skip to content

fix(swe-bench): validate model_params before reading generation settings - #476

Open
arekay-nv wants to merge 1 commit into
swe-layer-7from
swe-layer-8
Open

fix(swe-bench): validate model_params before reading generation settings#476
arekay-nv wants to merge 1 commit into
swe-layer-7from
swe-layer-8

Conversation

@arekay-nv

Copy link
Copy Markdown
Collaborator

What does this PR do?

Type of change

  • Bug fix
  • New feature
  • Documentation update
  • Refactor/cleanup

Related issues

Testing

  • Tests added/updated
  • All tests pass locally
  • Manual testing completed

Checklist

  • Code follows project style
  • Pre-commit hooks pass
  • Documentation updated (if needed)

Stack created with GitHub Stacks CLIGive Feedback 💬

score() reads the run's settings back from the report directory's config.yaml,
which yaml.safe_load() returns as plain dictionaries. It then handed that
mapping to SWEBenchScorer._generation_params(), which calls .model_dump() on
it, so the fleet scorer raised

    AttributeError: 'dict' object has no attribute 'model_dump'

on every run, after the plan and the work queue had been written but before a
single unit was dispatched.

Re-validate the mapping into ModelParams instead of re-implementing the field
selection here, so the fleet path and the single-service path stay in
agreement about which generation settings are forwarded to the service.
@arekay-nv
arekay-nv requested a review from a team as a code owner August 26, 2026 03:32
@github-actions

Copy link
Copy Markdown

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@github-actions
github-actions Bot requested a review from nvzhihanj August 26, 2026 03:33
@github-actions github-actions Bot added the size/normal PR Review Policy: <=500 non-test lines & <=20 files label Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/normal PR Review Policy: <=500 non-test lines & <=20 files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants