A workspace that stops mid-copy no longer crashes the server

If your workspace stopped or restarted while files were being copied into it, the server process could crash. That no longer happens.

User impact: Targeted change

A stopped workspace now fails its sync instead of crashing the server; related gateway errors are also addressed.

In mid-September we saw a burst of server crashes. We traced them to one case: files were being copied into a workspace just as that workspace stopped or restarted. The copy broke off, nothing caught the error, and the server process went down with it.

What changed

Automatic file sync into your workspace now treats a broken-off copy as a failed sync. The server keeps running.
The same fix covers workspace export, jobs sent to worker machines, and the security testing workspace.
Separately, some pages and replies failed with a brief gateway error even though the server was healthy. The server closed idle connections sooner than the layer in front of it expected. It now keeps them open long enough, so those errors should stop.

What you might notice

Usually nothing. If your workspace stops during a sync, that one sync fails. Nobody else is affected.