mirror of
https://github.com/Crosstalk-Solutions/project-nomad.git
synced 2026-10-17 05:14:19 +02:00
8c87b25343
The submit flow discarded the real failure reason and always returned the generic "Failed to submit benchmark results." to the UI. The most common cause is the leaderboard's one-per-hour rate limit (HTTP 429), which left users with no idea why their submission failed or that retrying shortly would also fail. - benchmark_controller: return a clear, actionable message. Name the rate limit explicitly on 429; otherwise pass through the underlying detail (repository error or a service validation message like "already submitted"), falling back to the generic only when we have nothing. - benchmark_service: attach the raw upstream `detail` to the thrown error so the controller can surface it. The frontend already renders the server `error` string, so no client change is needed. |
||
|---|---|---|
| .. | ||
| 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 | ||