read_reference/options: inconsistent 'value' semantics and mojibake in language names #20

New Issue

2026-09-19T08:22:33+01:00

gronod commented

2026-09-19 08:22:33 +01:00

Summary

Reference projections (read_reference and read_integration options) emit an inconsistent value field — sometimes the numeric id, sometimes the display name, sometimes an unrelated field (logo path, boolean) — and languages shows character-encoding corruption ("??????").

Environment

Binary: deployed darwin-amd64 build from develop @ d047d76
Ombi: 4.53.10 (https://ombi.i3omb.com), JWT auth

Reproduction

read_reference {"action":"genres","media":"movie"}        // Thriller: value "Thriller" (should be 53)
read_reference {"action":"genres","media":"tv"}            // Reality: value "Reality" (should be 10764)
read_reference {"action":"languages"}                        // several empty values; Kirghiz name "??????"
read_reference {"action":"watch_providers","media":"movie"} // value: id | name | logoPath mixed
read_integration {"action":"options","service":"radarr","resource":"profiles"} // id 6: value false

Expected

value holds a stable, typed meaning per category (e.g. the upstream id or the display value), and non-ASCII names decode correctly.

Actual

value falls back across heterogeneous fields: numeric id, name string, logoPath, even a boolean — so consumers can't rely on its type or semantics.
languages item for Kirghiz shows name: "??????" — upstream mojibake passed through (likely upstream charset loss; noted for completeness).

Cause

refOf picks the first present candidate from []string{"value"}-style fallback lists; when upstream lacks the preferred field an arbitrary sibling leaks into value. The mojibake is likely upstream data, but the tool should arguably not emit ?????? silently.

Correlation IDs

992602f2752d576a73cc778a (watch_providers), 0a66e063115859a57f50d178 (radarr profiles), f514f879938a27b3e3e7b200 (countries OK), plus genres/languages sweep calls

## Summary Reference projections (`read_reference` and `read_integration` `options`) emit an inconsistent `value` field — sometimes the numeric id, sometimes the display name, sometimes an unrelated field (logo path, boolean) — and `languages` shows character-encoding corruption (`"??????"`). ## Environment - Binary: deployed darwin-amd64 build from `develop` @ `d047d76` - Ombi: 4.53.10 (https://ombi.i3omb.com), JWT auth ## Reproduction ```json read_reference {"action":"genres","media":"movie"} // Thriller: value "Thriller" (should be 53) read_reference {"action":"genres","media":"tv"} // Reality: value "Reality" (should be 10764) read_reference {"action":"languages"} // several empty values; Kirghiz name "??????" read_reference {"action":"watch_providers","media":"movie"} // value: id | name | logoPath mixed read_integration {"action":"options","service":"radarr","resource":"profiles"} // id 6: value false ``` ## Expected `value` holds a stable, typed meaning per category (e.g. the upstream id or the display value), and non-ASCII names decode correctly. ## Actual - `value` falls back across heterogeneous fields: numeric id, name string, `logoPath`, even a boolean — so consumers can't rely on its type or semantics. - `languages` item for Kirghiz shows `name: "??????"` — upstream mojibake passed through (likely upstream charset loss; noted for completeness). ## Cause `refOf` picks the first present candidate from `[]string{"value"}`-style fallback lists; when upstream lacks the preferred field an arbitrary sibling leaks into `value`. The mojibake is likely upstream data, but the tool should arguably not emit `??????` silently. ## Correlation IDs `992602f2752d576a73cc778a` (watch_providers), `0a66e063115859a57f50d178` (radarr profiles), `f514f879938a27b3e3e7b200` (countries OK), plus genres/languages sweep calls

gronod added this to the M6 — Integration options and server-id discovery milestone 2026-09-19 08:58:05 +01:00

gronod added a new dependency 2026-09-19 08:58:14 +01:00

#17 read_integration options root_folders: name empty, path only in value

gronod referenced this issue from a commit

2026-09-19 14:11:13 +01:00

Fix #20: Make reference projection value deterministic and guard against mojibake labels

gronod referenced this issue

2026-09-19 14:39:29 +01:00

M6 integration options: settings projections and media server discovery #23

gronod closed this issue

2026-09-19 14:39:35 +01:00

Sign in to join this conversation.