Builds and live sync
A build runs on the server as a job, so it keeps going when you close the tab. Two devices open on the same project follow each other live.
A build is a job
A turn takes minutes, so the server does not hold the request open. It answers at once with a job and runs the build in a worker pool. Progress goes out over the project's event stream. The result is fetched when it is done.
Building a design.json from a file is a job too. Opening a .kicad_pcb or a
project .zip from the projects page is not: nothing is built, so the page
waits for the answer.
| What happens | Result |
|---|---|
| You close the tab mid-build | The build keeps running. Reopen the project on any device to see its stage and get the reply. |
| You send a second message while one builds | Refused with already building. Other projects are not blocked. |
| The model call fails, or credentials are missing, or the pipeline throws | The thread shows an error with the reason, and the message box comes back. |
soldermask serve --workers N sets how many builds run at once. The default is
2. One build's anneals and retries already use every core, so two builds at
once share them.
| Setting | Default under soldermask serve |
|---|---|
SOLDERMASK_ANNEAL_WORKERS | One anneal a core |
SOLDERMASK_ROUTER_RETRY_WORKERS | One Lightcycle retry a core, for a board that routes short |
SOLDERMASK_ROUTE_WORKERS | Three placements routed at once on 32 cores or more, one at a time below that |
A value you set in the environment wins over these.
Scripts can follow a job at /api/jobs/<id>, or send "wait": true to get the
result in one request. See the HTTP API.
Live sync
Two devices open on the same project share:
- the view
- the 3D camera
- the selection and the highlighted net
- the build quantity
- the version on screen
Move the 3D board on your desktop and the phone follows. Tap a part on the phone and the desktop picks it too. While the stream is connected, the readout shows nothing about it. It shows Sync off when the page has lost the server.
Each project has one event stream, at /api/events?project=<slug>. The last
change wins. Each device ignores the echo of its own moves, so two devices never
fight over the camera. Camera moves go out at most about 16 times a second. The
same stream carries build progress.
Limits. A stream holds a server thread for as long as it is open, and it cannot tell when its device has gone. So streams are capped at a third of the server's threads, and each ends after five minutes. The browser reconnects by itself.
A device that cannot get a stream still works. Its readout shows Sync off, the build reports through the job instead, and the stream picks up when a slot frees.
Sync needs the app's own server, one process per data directory. It is off in the standalone export.
Exports and files
Every file a fab, an assembler or KiCad needs is saved with the version. You can download one version's files, or the whole project as one zip.
Benchmarks
The benchmarks page shows what the shipped models and the pipeline score. It computes nothing: every number was written to disk by the run that measured it.