Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add meaningful GUI error when migration fails #1823

Closed
lidel opened this issue May 14, 2021 · 0 comments · Fixed by #1982
Closed

Add meaningful GUI error when migration fails #1823

lidel opened this issue May 14, 2021 · 0 comments · Fixed by #1982
Assignees
Labels
effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P3 Low: Not priority right now

Comments

@lidel
Copy link
Member

lidel commented May 14, 2021

Some power users may run into situation, where repo version is higher than one supported by ipfs-desktop:

021-05-13T22:01:23.422Z error: [ipfsd] start daemon Error: Initializing daemon...
go-ipfs version: 0.7.0
Repo version: 10
System version: amd64/windows
Golang version: go1.14.4
 
 Error: Your programs version (10) is lower than your repos (11).
Please update ipfs to a version that supports the existing repo, or run
a migration in reverse.
See https://github.com/ipfs/fs-repo-migrations/blob/master/run.md for details. 
 Command failed with exit code 1: D:\Users\foobar\AppData\Local\Programs\IPFS Desktop\resources\app.asar.unpacked\node_modules\go-ipfs\go-ipfs\ipfs.exe daemon --migrate --enable-gc --routing dhtclient
Error: Your programs version (10) is lower than your repos (11).
Please update ipfs to a version that supports the existing repo, or run
a migration in reverse.
See https://github.com/ipfs/fs-repo-migrations/blob/master/run.md for details.

IIUC this error lands in logs, but the user gets generic one with option to "restart" or "report github issue"
We should do better, and display console output to the user, so they can self-service.

@lidel lidel added the need/triage Needs initial labeling and prioritization label May 14, 2021
@lidel lidel added P2 Medium: Good to have, but can wait until someone steps up P3 Low: Not priority right now effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue and removed P2 Medium: Good to have, but can wait until someone steps up need/triage Needs initial labeling and prioritization labels May 21, 2021
@hacdias hacdias self-assigned this Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue P3 Low: Not priority right now
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants