Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Keep UI responsive and show progress when fetching data from GitHub, Steam Community, SteamDB, etc.

Aperta
  • Qualcosa non va?
#2,492 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python
Ambito
desktop, frontend, networking, performance

Direzione di ricerca

Start by locating the network-fetching paths used at startup and by “Check mod updates,” then trace how they interact with the frontend UI thread. Done should include responsive UI, visible operation status or progress, and proxy handling for the listed services, with tests or manual checks covering slow network conditions.

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

Descrizione

feature/improvement 🆕
Origin of idea

On the Windows build of RimSort, I noticed that the app frequently fetches data from GitHub, Steam Community, SteamDB, and other websites (e.g., on startup, when clicking "Check mod updates", etc.). While the required files have not finished downloading, the frontend UI stays in a "Not Responding" state with no indication of what is happening. On poor network conditions, the UI can remain unresponsive for a long time, which makes it easy for users to believe RimSort has crashed or frozen.

Suggestion/proposed solution?

Please keep the frontend UI responsive during these network operations, and provide visible progress/status feedback. For example:

  • Run all network fetching (GitHub, Steam Community, SteamDB, etc.) on background threads so the main UI thread is never blocked.

  • Show a progress bar or an indeterminate loading indicator while data is being fetched.

  • Display a status text describing the current operation (e.g., "Fetching data from GitHub...", "Checking mod updates...") and, if possible, which step/URL is currently being processed.

  • Ideally, respect the system proxy settings so users behind a proxy are not forced into direct connections.

Alternatives considered

Only adding a "please wait" dialog.

Additional context

RimSort appears to bypass the system proxy when accessing these sites, which makes the problem much worse in regions where direct access is slow or blocked.

Code of Conduct

I agree to follow this project's Code of Conduct

Duplicate Issue Check

I've checked for similar issues and didn't find anything

Wiki/FAQ Check

I've checked the Wiki for a solution and didn't find a solution

Lingua principale
Python
Stelle
1.2k
Fork
155
Merge medio
7h 23m
PR unite (30g)
62

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 RimSort/RimSort

Tutte le issue di RimSort/RimSort

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.