3 people 35e99d27c1 [2.0.x] fix: apply ByteStream deadline per-call, not on the memoized stub (#9413) (#9431) ...

The byteStreamStub lazy val applied withDeadlineAfter once, baking in an
absolute deadline that was reused for the store's whole (session-long)
lifetime. remoteTimeoutInSec after the first blob transfer, every later
ByteStream read/write was rejected with DEADLINE_EXCEEDED, so the remote
cache could neither upload nor download blobs >chunkSizeBytes for the rest
of the sbt server's life.

Derive a fresh stub with the deadline per RPC so each call gets its own
relative timeout.

Co-authored-by: Yannick Heiber <[email protected]>
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

2026-07-11 13:58:24 -04:00

..

src

[2.0.x] fix: apply ByteStream deadline per-call, not on the memoized stub (#9413) (#9431)

2026-07-11 13:58:24 -04:00