Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EZ] Fix config bug where interpolation happens too early #2236

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

EugenHotaj
Copy link
Contributor

There is currently a bug in config interpolation. E.g. given the following config:

name: REPLACE_ME
output_dir: ${name}/logs

When overriding name=some-override via the CLI, the expected config should be:

name: some-override
output_dir: some-override/logs

However, instead we get:

name: some-override
output_dir: REPLACE_ME/logs

This happens because OmegaConf resolves values under the hood when you try to access them.

Context

What is the purpose of this PR? Is it to

  • add a new feature
  • fix a bug
  • update tests and/or documentation
  • other (please add here)

Please link to any issues this PR addresses.

Changelog

What are the changes made in this PR?

  • See above

Test plan

Please make sure to do each of the following if applicable to your PR. If you're unsure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.

  • run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
  • add unit tests for any new functionality
  • update docstrings for any new or updated methods or classes
  • run unit tests via pytest tests
  • run recipe tests via pytest tests -m integration_test
  • manually run any new or modified recipes with sufficient proof of correctness
  • include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX

If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example

  • I did not change any public API
  • I have added an example to docs or docstrings

Copy link

pytorch-bot bot commented Jan 7, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/2236

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 4 Cancelled Jobs

As of commit 3bf3c9d with merge base 27fd3a1 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 7, 2025
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 23.95%. Comparing base (213f386) to head (3bf3c9d).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
torchtune/config/_parse.py 0.00% 1 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (213f386) and HEAD (3bf3c9d). Click for more details.

HEAD has 8 uploads less than BASE
Flag BASE (213f386) HEAD (3bf3c9d)
9 1
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2236       +/-   ##
===========================================
- Coverage   65.41%   23.95%   -41.47%     
===========================================
  Files         344      352        +8     
  Lines       20658    20847      +189     
===========================================
- Hits        13514     4993     -8521     
- Misses       7144    15854     +8710     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@RdoubleA
Copy link
Contributor

RdoubleA commented Jan 8, 2025

This is a great catch. You may need to update the unit tests to make sure the mock value returned by OmegaConf.load is an OmegaConf object. Would you also be able to modify test_parse_known_args in tests/torchtune/config/test_parse.py to test for this edge case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants