Skip to content

feature/gc-filesys-check#23

Merged
bgunnar5 merged 7 commits into
feature/db-garbage-collectionfrom
feature/gc-filesys-check
Oct 22, 2025
Merged

feature/gc-filesys-check#23
bgunnar5 merged 7 commits into
feature/db-garbage-collectionfrom
feature/gc-filesys-check

Conversation

@bgunnar5
Copy link
Copy Markdown
Owner

Adds checks for file system mounts when we're validating the existence of workspace paths. This will help keep database run entries from being deleted when the file system for their workspaces isn't accessible from the current machine.

Copy link
Copy Markdown

@jwhite242 jwhite242 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding functionality to detect this. Few more general thoughts and a question that I think I missed in the code:

  • Would be good to have some non-mocked tests in here to verify some of the functionality
  • Can you explain more how the machinery actually detects the special '/' root for ignoring it in other path searches since they all start with '/'? Is it the is_mount funcs from the stdlib that know the difference between it and another mounted system?

Comment thread tests/unit/db_scripts/test_garbage_collector.py Outdated
Comment thread tests/unit/db_scripts/test_garbage_collector.py Outdated
Comment thread tests/unit/db_scripts/test_garbage_collector.py
@bgunnar5
Copy link
Copy Markdown
Owner Author

@jwhite242 it's the psutil.disk_partitions() call that is able to distinguish the root '/' from different mount points. So in this PR that's all handled in the get_accessible_mounts() function of the utils.py module.

@bgunnar5 bgunnar5 merged commit 62d2e59 into feature/db-garbage-collection Oct 22, 2025
40 of 41 checks passed
@bgunnar5 bgunnar5 deleted the feature/gc-filesys-check branch October 22, 2025 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants