hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

(bugfix) Bound snapshot storage metadata scans #101

Merged
parkel merged 1 commits from issue-100-bound-storage-metadata-scans into master 2026-06-08 23:26:24 +02:00
Conversation 0 Commits 1 Files Changed 4 +77 -7
parkel commented 2026-06-08 23:19:17 +02:00
Owner
Copy Link

Summary

  • Add an optional max_entries limit to snapshot tree usage scans.
  • Use a bounded snapshot storage scan when backup workers record run/snapshot metadata.
  • Record scan_limited, entries_scanned, and max_entries with snapshot storage metadata so partial measurements are explicit.

Tests

  • .venv/bin/python manage.py test pobsync_backend.tests.test_run_stats pobsync_backend.tests.test_run_scheduled_config_source --verbosity 2
  • .venv/bin/python manage.py test pobsync_backend --verbosity 1

Related follow-up: #98.

Closes #100

## Summary - Add an optional `max_entries` limit to snapshot tree usage scans. - Use a bounded snapshot storage scan when backup workers record run/snapshot metadata. - Record `scan_limited`, `entries_scanned`, and `max_entries` with snapshot storage metadata so partial measurements are explicit. ## Tests - `.venv/bin/python manage.py test pobsync_backend.tests.test_run_stats pobsync_backend.tests.test_run_scheduled_config_source --verbosity 2` - `.venv/bin/python manage.py test pobsync_backend --verbosity 1` Related follow-up: #98. Closes #100
parkel added 1 commit 2026-06-08 23:19:17 +02:00
(bugfix) Bound snapshot storage metadata scans 9ece39b72e 
Limit snapshot storage scans recorded by backup workers so very large backup targets cannot make run finalization walk unbounded file trees. Limited scans now record scan_limited, entries_scanned, and max_entries in snapshot storage metadata.

Closes #100
parkel merged commit aac424e7ac into master 2026-06-08 23:26:24 +02:00
parkel deleted branch issue-100-bound-storage-metadata-scans 2026-06-08 23:26:24 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#101
Delete Branch "issue-100-bound-storage-metadata-scans"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?