Skip to content

fix(tasks): skip few-shot reuse warning for zero-shot tasks - #1372

Draft
LarryHu0217 wants to merge 1 commit into
huggingface:mainfrom
LarryHu0217:codex/avoid-zero-shot-fewshot-warning-801
Draft

fix(tasks): skip few-shot reuse warning for zero-shot tasks#1372
LarryHu0217 wants to merge 1 commit into
huggingface:mainfrom
LarryHu0217:codex/avoid-zero-shot-fewshot-warning-801

Conversation

@LarryHu0217

Copy link
Copy Markdown

Fixes #801

Summary

Keep the existing few-shot split inference, but only emit the evaluation-data reuse warning when the task actually requests one or more few-shot examples. Zero-shot tasks still fall back in the same way, without receiving a warning about a code path they do not use.

The regression test covers both sides of the behavior: zero-shot remains silent, while one-shot still emits the warning.

Validation

  • focused zero-shot/one-shot regression;
  • full task module, registry, and prompt-manager tests;
  • all 34 task unit tests;
  • Ruff lint and format checks;
  • git diff --check.

AI assistance disclosure: Codex was used to help prepare and validate this change.

Keep few-shot split inference unchanged, but only warn about reusing evaluation data when the task actually requests few-shot examples. Cover zero-shot silence and one-shot warning behavior.

Fixes huggingface#801
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] test split forced to hit Careful warning

1 participant