-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ENH]: add validation during garbage collection for empty file paths #4586
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
base: feat-gc-orchestrator-v2
Are you sure you want to change the base?
[ENH]: add validation during garbage collection for empty file paths #4586
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
f57dc9d
to
b8ab357
Compare
Add Defensive Validation for Empty File Paths in Garbage Collection This PR introduces a defensive check in the garbage collector orchestrator to validate that if no file paths are present during garbage collection, the current version and all of its ancestors must be version 0. The update adds a fail-fast invariant in code execution and includes a new test to confirm this behavior. It also includes refactoring of test mock infrastructure in TestSysDb to improve replica handling for version file paths. Key Changes: Affected Areas: This summary was automatically generated by @propel-code-bot |
a72bc81
to
5c86e1c
Compare
b8ab357
to
76c115d
Compare
5c86e1c
to
2191cf0
Compare
76c115d
to
02546b5
Compare
Description of changes
Adds a defensive check that validates that the current version is v0 if there are no file paths.
Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustAdded a test.
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?
n/a