mlcommons / mlcommons/logging

Description errors for variable that changed names

Open
#291 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
43
Forks
60
Avg merge
19h 56m
Merged PRs (30d)
3

Description

The training WG asked that we output a clearer error for variables that changed their names:
For example:

  • Here: opt_epsilon->opt_lamb_epsilon
  • Here: train_samples->dataset_ train_samples and train_samples-> total_train_samples

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the examples in PR 290 and issue 276, then trace where variable-name validation errors are generated in the Python library. Determine the intended wording for variables that changed names and verify that the relevant error cases are covered without regressing existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.