fix
patch
task/fix-sha256-proposal-id-passthrough
#1 / 1
fix: use split_id to recognise sha256 full IDs in _resolve_proposal_id
The full-ID passthrough check required a hyphen, so sha256:<64-hex> IDs always fell through to the list fetch with limit=200. Hubs capped below 200 returned 422 on every hub proposal read sha256:... call.
Fix: try split_id() first — valid prefixed or bare-hex full IDs return immediately without any network call. The legacy hyphenated-UUID check is kept as a fallback.
sha256:981ccb0e8446b8253d87e5ed34cb0eeb480b1dbf94070eb01526a8505f7eb99f
sha
+6
~3
symbols
sha256:55a7582e22cc6cceae2699fa489b8db1adabf8de42ba65f090fd5d0567d27eda
snapshot
+6
symbols added
~3
symbols modified
0
dead code introduced
Semantic Changes
9 symbols
+
TestResolveProposalIdSha256Passthrough
class
class TestResolveProposalIdSha256Passthrough L4023–4080
+
test_full_sha256_id_returned_as_is_no_network
method
method test_full_sha256_id_returned_as_is_no_network L4037–4052
+
test_hyphenated_uuid_still_returned_as_is
method
method test_hyphenated_uuid_still_returned_as_is L4073–4080
+
test_sha256_prefix_still_resolves_via_list
method
method test_sha256_prefix_still_resolves_via_list L4054–4071
← Older
Oldest on task/fix-sha256-proposal-id-passthrough
All commits
Newer →
Latest on task/fix-sha256-proposal-id-passthrough
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:981ccb0e8446b8253d87e5ed34cb0eeb480b1dbf94070eb01526a8505f7eb99f --body "your comment"
No comments yet. Be the first to start the discussion.