-
Notifications
You must be signed in to change notification settings - Fork 12
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
DM-44583: support manual config outputs in mocking system #420
Conversation
Previously we just looked at the storage classes to identify config, log, and metadata datasets that we shouldn't mock because they're written by the execution system. But this prevented tasks from being able to have regular outputs using those storage classes; we *do* want to mock those.
This works around the fact we can't necessarily see the full pipeline graph in mock_pipeline_graph and hence can't identify when a special unmocked output (e.g. a config) is read in by a later task in order to mark the dataset type as unmocked in the later task.
74619de
to
becea23
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #420 +/- ##
==========================================
- Coverage 81.07% 80.92% -0.16%
==========================================
Files 95 95
Lines 10833 10818 -15
Branches 2060 2064 +4
==========================================
- Hits 8783 8754 -29
- Misses 1705 1718 +13
- Partials 345 346 +1 ☔ View full report in Codecov by Sentry. |
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.
The code looks fine from what I understand, but I do not understand the mocking system of the pipeline graphs...
There might need to be some sort of uv patch required as well? |
Virtual env environment variable is no longer supported.
b6a005f
to
093c821
Compare
Checklist
doc/changes