feat(#92): phase 5 — GC expired fetch mpack cache entries (FMC_19–FMC_20)
- gc_fetch_mpack_cache(session, repo_id): query expired MusehubFetchMPackCache rows, call backend.delete on each R2 object, delete the DB rows - _handle_gc in worker.py: call gc_fetch_mpack_cache after run_gc so cache cleanup runs on every gc job without touching run_gc's existing logic - Test FMC_20: expired rows + R2 objects deleted; fresh rows untouched
sha256:f58d788df3ccdda8f8987b428418db655a38582309239b99d7b9715ea6dff618
sha
+4
~7
symbols
3 changed · 972 in snapshot
files
sha256:8fb09937fbbc8661df58c2c642a6fb9c3942ac79818a755193cc60e51bd7e49f
snapshot
+4
symbols added
~7
symbols modified
3
files changed
972
files in snapshot
0
dead code introduced
Semantic Changes
11 symbols
+
test_fmc_20_gc_deletes_expired_rows_and_r2_objects_leaves_fresh_untouched
function
async_function test_fmc_20_gc_deletes_expired_rows_and_r2_objects_leaves_fresh_untouched L320–378
Files Changed
~3
972 in snapshot
~3
972 in snapshot
Older
feat(#92): phase 4 — enqueue fetch.mpack.prebuild on push (FMC_1…
sha256:d50f9cf9829dfbe35721a23b81ad256c729ddf9dd565a0a9e56d27847e255632
All commits
Newer
chore: rename migration 0072 → 0071 (0071 prose backfill was she…
sha256:294f5f41277b624e1107a61b102d88c784a5380c2c436095da176538d74f38ba
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:f58d788df3ccdda8f8987b428418db655a38582309239b99d7b9715ea6dff618 --body "your comment"
No comments yet. Be the first to start the discussion.