This warning should be more discreet, it shouldn't show up when you're about to just run.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 264
- Avg merge
- 1d 13m
- Merged PRs (30d)
- 23
Description
elif not valid_for_eval:
log.warning(
f"{dataset} not compatible with evaluation. "
"Removing this dataset from the list."
)
rm.append(dataset)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the shown elif not valid_for_eval logging block and inspect how this warning behaves when the project is run. Determine the intended quieter behavior for the incompatible-dataset warning, while preserving removal of incompatible datasets. Done means the warning is discreet in the described run path and the dataset handling still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100