fix: stream mpack downloads without size cap
_urllib_do gains an optional max_bytes param (default: MAX_RESPONSE_BYTES). The mpack GET in fetch_mpack passes max_bytes=None, streaming in 1 MiB chunks instead of buffering with a hard 64 MiB ceiling. API responses still use the default cap for OOM protection.
sha256:6b91dc90e1c59c5209b764a276c1ee824bd369320a454a403d28ce79890103f2
sha
~3
symbols
1 changed · 1067 in snapshot
files
sha256:85bdbf26df8c65f8a1bcfbdf9f460a4c4602aa7970e42de17e6f328b4e5a5a00
snapshot
~3
symbols modified
1
file changed
1067
files in snapshot
0
dead code introduced
Semantic Changes
3 symbols
Files Changed
~1
1067 in snapshot
~1
1067 in snapshot
Older
merge: pull local/dev — resolve trivial _EXT_MAP symbol conflict…
sha256:c5131d76c6eada02939111fda4aa8e51b0c1456b9983727cfd6be101916de14e
All commits
Newer
Merge 'task/fix-branch-delete-dry-run' into 'dev' — proposal: Fi…
sha256:18e585c043b10139697a2d40412cf49b2efd39ac6366827a41299037fc915f4c
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:6b91dc90e1c59c5209b764a276c1ee824bd369320a454a403d28ce79890103f2 --body "your comment"
No comments yet. Be the first to start the discussion.