Front end: set a machine up for a development build from the window

Aperta
  • Qualcosa non va?
#575 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend, desktop

Direzione di ricerca

Read gui/src/solprop_gui/ui/setup_dialog.py and src/solprop/service/install.py (setup_script, copy_wheels), then inspect native/scripts/fetch_wheel.py and the Linux wheel constraints from #570. Trace how the dialog prepares and shows the setup script before it runs. Done means a development build can prepare a fresh Linux machine from the dialog, explain when no matching native wheel exists, and complete a run; the issue says this is recorded manually.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: gui enhancement priority: low
What is missing

Run → Machines… → Set up solprop there… (from #571, solprop.service.install) installs solprop at the window's version from PyPI, or from wheels the user adds. A release works. A development build does not: PyPI has no 0.2.1.devN+g…, so the dialog refuses it unless wheels are added, and the user has no easy way to get wheels that work on the machine. The window's own solprop wheel can be built anywhere (pure Python), but solprop-native must be a Linux wheel for the machine, and the one CI builds per commit needs glibc 2.35 and a system FFTW (#570).

Why it matters

Testing the front end's remote machines against a branch needs a hand-made environment on each machine today (a checkout, a light sync and a borrowed FFTW). A developer, or a user on a pre-release, cannot set a machine up from the window.

Context
  • src/solprop/service/install.py (setup_script, copy_wheels), gui/src/solprop_gui/ui/setup_dialog.py.
  • #570, CI's Linux native wheel.
  • native/scripts/fetch_wheel.py, which finds a CI wheel for a commit.
To do
  • After #570, let the setup dialog fetch the right wheels for a development build itself: solprop's, built from the checkout, and solprop-native's for the machine's platform from CI, as fetch_wheel.py finds them.
  • Say in the dialog when no matching native wheel exists (native changed and CI has not built it), and how to proceed.
  • Must not change: a release installs from PyPI with no wheels; nothing runs on the machine before the user has seen the script.
Done when

A window running a development build sets up a fresh Linux machine (glibc 2.28+, no system FFTW, no compiler) from the dialog alone, and a run started there finishes; recorded by hand on a workstation, since no CI lane has one.

🤖 Generated with Claude Code

Lingua principale
Python
Stelle
3
Fork
3
Merge medio
8h 37m
PR unite (30g)
159

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LupoLab/solprop

Tutte le issue di LupoLab/solprop

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.