Skip to content

FIX: reject dataset size limits a scenario would ignore - #3082

Merged
Richard Lundeen (richlundeen) merged 3 commits into
microsoft:mainfrom
u7k4rs6:fix/dataset-limit-not-applicable
Oct 12, 2026
Merged

Richard Lundeen (richlundeen) merged 3 commits into
microsoft:mainfrom
u7k4rs6:fix/dataset-limit-not-applicable

Conversation

@u7k4rs6

@u7k4rs6 Utkarsh Bahuguna (u7k4rs6) commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Some scenarios silently ignored max_dataset_size, and the exploitation one ignored every dataset option. The resolver now rejects those with a clear error instead, for both launch and estimate, so the CLI and API behave the same. "default" and dataset names still work where they did before. I also dropped a max dataset size flag from a garak doc example since it never did anything. The new tests fail on main.

Fixes #3081

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 62f37062-d036-4bc1-a880-31728ad4b050
@richlundeen
Richard Lundeen (richlundeen) added this pull request to the merge queue Oct 12, 2026
Merged via the queue into microsoft:main with commit 90e98c3 Oct 12, 2026
55 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.

BUG: max_dataset_size is silently ignored by some garak scenarios

2 participants