client: use inactivity timeout for status stream shutdown by silvin-lubecki · Pull Request #6396 · moby/buildkit (original) (raw)

Instead of using a fixed 3-second timeout after solve completion, use an inactivity-based timeout that waits 5 seconds since the last received status message. This prevents premature stream closure when status messages are still being delivered through slow connections (e.g., proxied environments).

Also ignore context.Canceled errors in the status goroutine to avoid failing builds when the inactivity timeout triggers - the build itself succeeded, we just may have missed some final status messages.

Signed-off-by: Silvin Lubecki silvin.lubecki@docker.com