Skip to content

fix: use consistent readable model labels - #166

Merged
sadsfae merged 2 commits into
quadsproject:developmentfrom
sjug:fix/harness-model-display-names
Sep 29, 2026
Merged

sadsfae merged 2 commits into
quadsproject:developmentfrom
sjug:fix/harness-model-display-names

Conversation

@sjug

@sjug sjug commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

PERFSCALE-5951

Use one Python helper for model display names across onboarding, admin responses, and generated OpenCode, Pi, and OMP configurations. Labels omit the publisher and GGUF packaging suffixes while preserving model variants, API identifiers, token scopes, and configured defaults. OMP downloads retain explicit operator-defined names.

Replace the frontend naming regex with server-supplied labels, including saved selections for offline models. Add regressions for the four approved profiles, raw-ID fallbacks, private-model visibility, operator-name precedence, and unchanged configuration identifiers.

Validation: 2,886 tests passed with 93.82% coverage, including real Chromium interaction checks. Ruff lint and formatting, strict mypy, ShellCheck, JavaScript syntax checks, and git diff --check passed. Validation used the separate one-line lockfile correction required by development’s release bump.

Use a shared Python helper for onboarding, admin responses, and generated
OpenCode, Pi, and OMP configuration names. Preserve raw API identifiers,
token scopes, defaults, and explicit OMP operator names.

Replace frontend normalization with server-provided labels, including
saved offline selections. Cover approved profiles, fallback labels,
private-model visibility, and identifier preservation with regressions.

Refs: PERFSCALE-5951
Match the locked project version to 0.1.0-dev.2 so locked dependency
installation succeeds. Dependency versions are unchanged.

@ttlogan ttlogan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads clean. The display label now gets derived once, server-side, in model_display_name(), and every surface routes through it: onboarding model_names, the AdminNodeResponse model_display_name computed field, and all three harness/config generators. Raw IDs stay intact as the request identity, only the visible label changes, which is the right split. The GGUF/MTP suffix stripping keeps the edge cases (publisher/-GGUF, model-MTP) intact and the tests cover them. Also nice to have the duplicated JS displayName dropped in favor of the single server-supplied map.

@sadsfae
sadsfae merged commit e7678c5 into quadsproject:development Sep 29, 2026
3 checks passed
@sjug
sjug deleted the fix/harness-model-display-names branch September 29, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants