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:f41ad124522a3311d93141ecde90442958b5d0bc6dd3290f137959f6101838ae
snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:6797e2d0dfbcb290f6034f4111bd9930a281fcf72c75d6646e61a85165875b0c --body "your comment"
No comments yet. Be the first to start the discussion.