service_manager: ONNX Runtime auto-install (hero_voice / hero_embedder / hero_editor) #94

New issue

Open

opened 2026-05-07 19:11:44 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-05-07 19:11:44 +00:00

Owner

Tracked from #90.

The upstream nu modules for hero_voice / hero_embedder / hero_editor each install libonnxruntime.so.1.25.1 into ~/hero/bin/ alongside the binaries (download from the Forgejo release or microsoft/onnxruntime upstream). This is a runtime prerequisite — the binaries crash at startup without it.

The v2 ports declare ORT presence implicitly (e.g. hero_editor sets ORT_DYLIB_PATH) but do NOT install the .so. Operator must run service_voice install_ort once before service start.

Fix: add an install_ort helper in service_manager::lib (downloads libonnxruntime.so.<ver> from upstream or forge), and have each ONNX-using service's install call it as a prerequisite step.

Code-not-data design means each service decides whether to install ORT in its install body.

Limitation: in: hero_voice.rs, hero_embedder.rs, hero_editor.rs.

Tracked from #90. The upstream nu modules for hero_voice / hero_embedder / hero_editor each install `libonnxruntime.so.1.25.1` into `~/hero/bin/` alongside the binaries (download from the Forgejo release or microsoft/onnxruntime upstream). This is a runtime prerequisite — the binaries crash at startup without it. The v2 ports declare ORT presence implicitly (e.g. hero_editor sets `ORT_DYLIB_PATH`) but do NOT install the .so. Operator must run `service_voice install_ort` once before `service start`. **Fix**: add an `install_ort` helper in `service_manager::lib` (downloads `libonnxruntime.so.<ver>` from upstream or forge), and have each ONNX-using service's `install` call it as a prerequisite step. Code-not-data design means each service decides whether to install ORT in its `install` body. `Limitation:` in: hero_voice.rs, hero_embedder.rs, hero_editor.rs.