velxio/backend
David Montero 33ee270ae1 compile: arduino-cli builds no longer queue behind ESP-IDF builds
One Semaphore(2) gated every compile, so while two ESP32 builds ran (cmake +
ninja, minutes on a cold cache) an Arduino Uno blink sat 'compiling' for as
long as they took. Two lanes now: heavy (ESP-IDF, still 2 — the VPS load
constraint is real) and light (arduino-cli boards, 3), plus a console line
when a job is queued so the wait is visible instead of looking like a hung
build. The per-target lock that keeps concurrent builds out of one ESP-IDF
build dir is unchanged.
2026-08-18 22:08:54 +02:00
..
app compile: arduino-cli builds no longer queue behind ESP-IDF builds 2026-08-18 22:08:54 +02:00
board-indexes fix(docker): vendor drazzy.com board index + seed missing indexes at boot 2026-07-17 06:41:44 +02:00
scripts
…
sdk
…
tests fix(espidf): ccache hash_dir=false so build variants share objects; log ninja/cmake timeouts 2026-08-17 19:15:28 +02:00
.env.example
…
Dockerfile fix(docker): vendor drazzy.com board index + seed missing indexes at boot 2026-07-17 06:41:44 +02:00
debug_qemu.py
…
mcp_server.py
…
mcp_sse_server.py
…
requirements.txt fix(ci): cap mcp below 2.0 — the backend suite has not run since 2026-07-29 2026-08-10 17:14:39 +02:00