-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[release/4.0] Improve unique directory generation for temp files #7528
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
Conversation
Refactor unique directory creation logic to use random file names.
Co-authored-by: Copilot <[email protected]>
|
Need to fix the build, will first do that here -- darc-release/4.0-59b01119-72fa-4ec9-8595-f64b50c7a93e - #7470 |
tarekgh
left a comment
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.
LGTM. The build issue is not directly related to the change. Eric is fixing that.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/4.0 #7528 +/- ##
============================================
Coverage 68.89% 68.89%
============================================
Files 1470 1470
Lines 274081 274082 +1
Branches 28405 28405
============================================
+ Hits 188836 188840 +4
Misses 77928 77928
+ Partials 7317 7314 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
/azp run MachineLearning-CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Backport of #7520 to release/4.0
/cc @ericstj
Customer Impact
For each model opened ML.NET would leave behind a temp folder which would slowly accumulate in the temp directory. It also had an algorithm for temp folder creation which would linearly degrade with each new folder.
Testing
Tested fix that the folder is deleted and the creation algorithm does not degrade linearly if folders happen to be left behind because it uses GetTempFileName to produce significantly random folder name candidates.
Risk
This fix doesn't clean up past folders, we should release-note that users may want to do this manually.