From 4a03cd7e778fd50218c5c7355c07517cb04eb712 Mon Sep 17 00:00:00 2001 From: jamiepine <32987599+jamiepine@users.noreply.github.com> Date: Sat, 3 Oct 2026 09:32:12 +0000 Subject: [PATCH] fix(backend): log when VOICEBOX_FORCE_CPU forces the CPU device Without a trace the Settings GPU label and /health keep reporting CUDA while generation runs on CPU, so the user has no way to confirm the override engaged. --- backend/backends/base.py | 1 + 1 file changed, 1 insertion(+) diff --git a/backend/backends/base.py b/backend/backends/base.py index fa1c90ac..83acf2c3 100644 --- a/backend/backends/base.py +++ b/backend/backends/base.py @@ -108,6 +108,7 @@ def get_torch_device( # Stripped: on Windows, where this override matters most, it is usually set # through the GUI environment editor. if os.environ.get(FORCE_CPU_ENV_VAR, "").strip() == FORCE_CPU_ENABLED_VALUE: + logger.info("%s=%s set, forcing CPU device", FORCE_CPU_ENV_VAR, FORCE_CPU_ENABLED_VALUE) return "cpu" if force_cpu_on_mac and platform.system() == "Darwin":