-
Notifications
You must be signed in to change notification settings - Fork 38
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
cleanup dvcyaml #615
cleanup dvcyaml #615
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #615 +/- ##
==========================================
+ Coverage 89.70% 89.72% +0.01%
==========================================
Files 43 43
Lines 2983 2987 +4
Branches 247 248 +1
==========================================
+ Hits 2676 2680 +4
Misses 268 268
Partials 39 39
☔ View full report in Codecov by Sentry. |
@@ -121,6 +121,9 @@ def _init_cleanup(self): | |||
if f and os.path.exists(f): | |||
os.remove(f) | |||
|
|||
if self.dvc_file and os.path.exists(self.dvc_file): |
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.
I remember we had a discussion the first time we added the make_dvcyaml about not wanting to remove it on cleanup #366 (comment)
Do you think the concerns no longer apply (the config for sklearn is now auto-generated) and we can consider the dvclive/dvc.yaml not modifiable?
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.
Nevermind, it looks like we are already overwriting in the code, so we never preserved the existing dvcyaml 😅
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 changes look good to me, and it is consistent with the behavior we already applying *#615 (comment).
My only worry is that I am not understanding the issue behind #611 and when this is a fix. I assume that this is a fix only if Live
gets instantiated before params_show
is called?
@daavoo Where are we overwriting in the code? Is this PR doing anything then? 😅 |
This reverts commit a0de508.
Lines 86 to 116 in d261760
This only happens when
Yes, it makes the behavior consistent with the rest of the DVCLive-generated files, where we clean up at |
I wonder if we need to be so particular anymore about which files to drop inside the dvclive dir or if we should just drop the whole dir. Seems just as likely that someone will end up with stale files than deleting something someone wanted to keep. AFAIR we used to drop more aggressively before #102, but maybe we are more clear now that the dvclive dir should be a separate dir managed only by dvclive. |
Fixes #611