fix: isolate S3 PUT in _push_presign from shared H2 bench client
CF H2 connection pool state poisons S3 TLS sessions — fresh H1 client per S3 upload prevents SSLV3_ALERT_BAD_RECORD_MAC on presign path.
sha256:792f52a36f3956ea147fc36a965fcb5e13cf80f6c16f0438ca30b2dd274d79e0
sha
sha256:f28b8fa2a02227a50088a4fbc252c74e3e38d43694cbd5b2a44d9b9483b8e00b
snapshot
Older
fix(bench): auto-route M+ push to presign on staging/prod; add s…
sha256:edb137f64af4f4b7c5698753f0f18e4762e305f002b32963fc51a99be37c3ea1
All commits
Newer
fix: secrets.sh now owns all env-specific config, not just secrets
sha256:aa5b0fb2c2cb3ee3829d265c83326caad1a0d9a4c8218e833a0e5b6a02e14045
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:792f52a36f3956ea147fc36a965fcb5e13cf80f6c16f0438ca30b2dd274d79e0 --body "your comment"
No comments yet. Be the first to start the discussion.