-
Notifications
You must be signed in to change notification settings - Fork 489
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
Conversation
🔗 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. ✅ No FailuresAs of commit 2bab3ec with merge base e420bc0 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2236 +/- ##
==========================================
- Coverage 65.41% 64.31% -1.11%
==========================================
Files 344 352 +8
Lines 20658 20569 -89
==========================================
- Hits 13514 13228 -286
- Misses 7144 7341 +197 ☔ View full report in Codecov by Sentry. |
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 |
@RdoubleA added ptal when you get a chance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome, will merge once CI is green
@EugenHotaj looks like one more test needs to be fixed, you can also run tests locally with |
Ah missed one of the tests, updated |
There is currently a bug in config interpolation. E.g. given the following config:
When overriding
name=some-override
via the CLI, the expected config should be:However, instead we get:
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
Please link to any issues this PR addresses.
Changelog
What are the changes made in this PR?
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.
pre-commit install
)pytest tests
pytest tests -m integration_test
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