mirror of
https://github.com/Crosstalk-Solutions/project-nomad.git
synced 2026-10-17 05:14:19 +02:00
2aa55a43ec
Benchmarks execute as a BullMQ job in the queue worker, but /api/benchmark/status and the 409 double-run guards read the web process's in-memory BenchmarkService, which never sees the run. Status always read idle, and a second POST /api/benchmark/run was accepted mid-flight and queued behind the first. Status now comes from the queue, the one place both processes can see. The worker publishes each stage on its job via job.updateProgress(), and resolveBenchmarkStatus() reports the active job's stage, "starting" for a job still queued, or the local status for a sync=true run. The status endpoint and all three run guards read it. If the queue can't be read they fall back to the local status, as before. Closes #1326 |
||
|---|---|---|
| .. | ||
| benchmark_controller.ts | ||
| chats_controller.ts | ||
| collection_updates_controller.ts | ||
| conditions_controller.ts | ||
| creator_packs_controller.ts | ||
| docs_controller.ts | ||
| downloads_controller.ts | ||
| drug_reference_controller.ts | ||
| easy_setup_controller.ts | ||
| home_controller.ts | ||
| maps_controller.ts | ||
| nomad_md_controller.ts | ||
| ollama_controller.ts | ||
| openapi_controller.ts | ||
| rag_controller.ts | ||
| settings_controller.ts | ||
| supply_depot_controller.ts | ||
| system_controller.ts | ||
| zim_controller.ts | ||