13cbcf5ed3
_resolve_library_components does minutes of synchronous filesystem work for a big library (FastLED: BFS over every header + copying thousands of files) directly inside async compile(), starving the event loop: the /api/compile/start response never flushed and clients timed out at 30s while the build itself was healthy. Run it via asyncio.to_thread like the cmake and ninja steps already do. |
||
|---|---|---|
| .. | ||
| app | ||
| board-indexes | ||
| scripts | ||
| sdk | ||
| tests | ||
| .env.example | ||
| Dockerfile | ||
| debug_qemu.py | ||
| mcp_server.py | ||
| mcp_sse_server.py | ||
| requirements.txt | ||