fix: enqueue mpack.index after every push (TDD)
mpack.index was missing from job_types_for_push — byte-range index never populated, causing full mpack downloads (100s MB) on every page load. Now always enqueued alongside intel.structural for all domains. 4 tests cover code/midi/None domains + integration via enqueue_push_intel.
sha256:fa68fb6b242d872f0f8f8a300e4e7bad498a4dd17fdc76ddd87245b460e6aa47
sha
+13
~1
symbols
sha256:87fa1fc6384fc87e7a5fd3e1585bc7d3994597d192740239bb58806fc6d9fbb0
snapshot
+13
symbols added
~1
symbol modified
0
dead code introduced
Semantic Changes
14 symbols
+
test_MIE1_mpack_index_in_code_push_jobs
function
function test_MIE1_mpack_index_in_code_push_jobs L30–37
+
test_MIE2_mpack_index_in_midi_push_jobs
function
function test_MIE2_mpack_index_in_midi_push_jobs L44–50
+
test_MIE3_mpack_index_when_no_domain
function
function test_MIE3_mpack_index_when_no_domain L57–60
+
test_MIE4_enqueue_push_intel_creates_mpack_index_job
function
async_function test_MIE4_enqueue_push_intel_creates_mpack_index_job L68–97
Older
chore: bump version to 0.2.0rc11; typing audit clean + all test fixes
sha256:ad616c6113d6c00f4efed6b2993734ca46d3e9b5bee25addd4ce8ae6b57136e5
All commits
Newer
feat: resurrect process_mpack_index_job with byte-range indexing (TDD)
sha256:8a7ff43f27504c1f6abba59ffbab3dc89bd1d8bcfa4c57f6e280286d1a58195a
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:fa68fb6b242d872f0f8f8a300e4e7bad498a4dd17fdc76ddd87245b460e6aa47 --body "your comment"
No comments yet. Be the first to start the discussion.