fix
BREAKING
task/push-mpack-put-timeout
#1 / 1
fix: scale presigned mpack PUT timeout with payload size (issue #40)
Large mpack uploads were hitting the global 300s timeout on slow uplinks. aaronrene/scooling reproduced this: ~36 MB at ~90 KB/s needs ~390s, which exceeded _TIMEOUT_SECONDS.
Adds _mpack_put_timeout(size_bytes): max(1800, size/50_000) capped at 7200s. push_mpack_put now uses this instead of the global API timeout. MUSE_PUSH_TIMEOUT_SECONDS env var overrides for ops/testing.
The global _TIMEOUT_SECONDS is unchanged — all other API calls keep 300s.
sha256:b9e80dbc5ca7d0bed2975a744af328796584ca4ed2f0dbda600a49d26be8d34e
sha
+20
~2
symbols
sha256:ec4eb06a0de2a0126217fca2ea318fac963e9c8ecbac68f347ff16d3f6ffed33
snapshot
+20
symbols added
~2
symbols modified
0
dead code introduced
Semantic Changes
22 symbols
+
test_pt1_small_payload_gets_floor_timeout
function
function test_pt1_small_payload_gets_floor_timeout L42–46
+
test_pt2_large_payload_exceeds_floor
function
function test_pt2_large_payload_exceeds_floor L51–55
+
test_pt4_computed_timeout_passed_to_urllib_do
function
function test_pt4_computed_timeout_passed_to_urllib_do L68–77
+
test_pt5_env_var_overrides_computed_timeout
function
function test_pt5_env_var_overrides_computed_timeout L82–90
+
test_pt6_env_var_absent_uses_computed_default
function
function test_pt6_env_var_absent_uses_computed_default L95–105
+
test_pt7_global_timeout_does_not_affect_put_timeout
function
function test_pt7_global_timeout_does_not_affect_put_timeout L110–124
← Older
Oldest on task/push-mpack-put-timeout
All commits
Newer →
Latest on task/push-mpack-put-timeout
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:b9e80dbc5ca7d0bed2975a744af328796584ca4ed2f0dbda600a49d26be8d34e --body "your comment"
No comments yet. Be the first to start the discussion.