Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Auto-Reload of the DB-migration page when upgrading

Open
#10,861 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
frontend

Research direction

Start at the DB-migration page and compare its behavior with the migration-page-auto-refresh branch linked in the issue. Verify that migration progress updates without interaction and that the page reaches the actual app UI when the upgrade finishes.

Written by the indexing model from the issue text.

Description

enhancement needs-triage
Feature description

It would be great if the DB-migration page would update itself and finally switch to the actual app UI when it is done.

Problem or use case

Currently when a DB upgrade is in progress a static text page is shown with the current log output.
But this page does not update by itself.
So without user interaction it will never go to the actual app, once the migration is done, or show any progress.

Alternatives or workarounds

I wrote this line of code to fix this:
https://github.com/Finomosec/syncthing/tree/migration-page-auto-refresh

Creating PRs is currently blocked. So please feel free to pull it over from your end.

Dominant language
Go
Stars
89.7k
Forks
5.5k
Avg merge
6h 27m
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from syncthing/syncthing

All issues in syncthing/syncthing

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.