test: regression coverage for issue #54 — proposal merge sha256 ID 422
Two tests added to TestProposalMerge422Regression:
1. test_merge_sha256_id_makes_no_list_call: exercises run_proposal_merge with a full sha256:<64-hex> proposal ID end-to-end, asserting that no proposals list endpoint call is made. The bug was that the old full-ID check required a hyphen, so sha256 IDs fell through to _resolve_proposal_id's list fetch (?limit=200). Servers capped at limit=100 returned 422 on that call, blocking every CLI merge.
2. test_merge_prefix_id_calls_list_but_not_with_limit_exceeding_server_cap: asserts _PROPOSAL_PREFIX_RESOLVE_LIMIT <= 200 (the server PaginationParams cap), so short-prefix resolution cannot trigger a 422 on the current server.
sha256:e8657b59054d266bfe40405e8bae9af28d392c279ecf013cf8f35b96bb81e785
sha
sha256:6f6bd9847e89a758bca3c7d3dcbf9be8947cfe69629325d513df7a5a8f1f78c3
snapshot
← Older
Oldest on task/issue-54-regression-test
All commits
Newer →
Latest on task/issue-54-regression-test
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:e8657b59054d266bfe40405e8bae9af28d392c279ecf013cf8f35b96bb81e785 --body "your comment"
No comments yet. Be the first to start the discussion.