Skip to content

feat(profiles): import and persist worker count - #34

Merged
luminescq merged 1 commit into
luminescq:mainfrom
mrddt-tech:feat/profile-worker-count
Oct 5, 2026
Merged

luminescq merged 1 commit into
luminescq:mainfrom
mrddt-tech:feat/profile-worker-count

Conversation

@mrddt-tech

Copy link
Copy Markdown
Contributor

Problem

Server profiles did not retain the configured total worker count. On import, a missing value caused the UI to use its legacy hash-count fallback instead.

Root cause

ProfileData had no workers field, so the value could not round-trip through the on-disk profile or the generated Wails model.

Implementation

  • Add optional workers to ProfileData and the generated TypeScript model.
  • Import it into the local server power value, including an already cached matching server.
  • Persist it from add, edit, and custom qwdtt-link profile imports.
  • Clarify that the slider represents the total number of worker threads.

Tests

  • go test ./...
  • cd frontend && npm test -- --run
  • GOOS=windows GOARCH=amd64 go test .
  • Windows production build

Observed behavior

Manually tested on Windows 10: a configured worker count is retained across restart and used by the connection flow.

Trade-offs

Absent or zero workers remains backward compatible: existing profiles keep the calculated fallback and are not rewritten solely to add a default.

@mrddt-tech
mrddt-tech marked this pull request as ready for review September 7, 2026 13:32
@luminescq
luminescq merged commit c12b37e into luminescq:main Oct 5, 2026
luminescq added a commit that referenced this pull request Oct 5, 2026
…tion — валидация workers из qwdtt-ссылки (подпись слайдера оставлена от #34)

# Conflicts:
#	frontend/src/modals/Add-server.tsx
#	frontend/src/modals/Edit-server.tsx
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.

2 participants