The Space logs said "onnxruntime has no CUDA provider", which is why the
probe kept reporting cpu on ZeroGPU hardware. renikud-plus depends on
`onnxruntime` (the CPU build) and we ask for `onnxruntime-gpu`; both wheels
install into the same onnxruntime/ directory, so whichever pip writes last
wins. With the GPU wheel first in the file, renikud-plus's CPU wheel
overwrote it and CUDAExecutionProvider disappeared.
Confirmed in a clean linux/amd64 container:
gpu installed last -> [Tensorrt, CUDA, CPU]
cpu installed last -> [Azure, CPU]
Move onnxruntime to the end of every requirements file. The Docker image
happened to land the right way round already, so this is a no-op there —
which is exactly the problem, so the build now asserts the provider
survived rather than printing it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0138DB6F6YxWtYWy7WNaLAsU
