gabriel / musehub public
fix patch fix/mpack-object-reads #1 / 1
AI Agent gabriel · 118 days ago · May 20, 2026 · Diff

fix: use read_object_bytes for mpack:// objects in README, raw, and blame

Objects pushed via the MPack wire format are stored with storage_uri mpack://sha256:<id> — they live inside a pack file, not as standalone S3 objects. Direct storage.get(object_id) always returns None for these.

Switch _fetch_readme, the raw file endpoint (ui_tree), and the blame file-content fetch (ui_blame) to look up the MusehubObject row and call read_object_bytes(), which handles both s3:// and mpack:// URIs.

sha256:6797e2d0dfbcb290f6034f4111bd9930a281fcf72c75d6646e61a85165875b0c sha
sha256:ff5869162061571b575399e1ae984b5ffed503e098269d5059aa1d5cabc6c06e parent
+3 ~5 symbols
sha256:f41ad124522a3311d93141ecde90442958b5d0bc6dd3290f137959f6101838ae snapshot
+3
symbols added
~5
symbols modified
0
dead code introduced
Semantic Changes 8 symbols
~ musehub/api/routes/musehub/_ui_helpers.py .py 1 symbol added, 2 symbols modified
+ _read_object_bytes import import _read_object_bytes L20–20
~ _fetch_readme
~ _get_storage_backend
~ musehub/api/routes/musehub/ui_blame.py .py 1 symbol modified
~ blame_page
~ musehub/api/routes/musehub/ui_tree.py .py 2 symbols added, 2 symbols modified
+ MusehubObject import import MusehubObject L26–26
+ _read_object_bytes import import _read_object_bytes L27–27
~ _get_storage_backend
~ raw_file_semantic
← Older Oldest on fix/mpack-object-reads
All commits
Newer → Latest on fix/mpack-object-reads

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:6797e2d0dfbcb290f6034f4111bd9930a281fcf72c75d6646e61a85165875b0c --body "your comment"