Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improve UX when $IPFS_PATH/api exists and API is offline

See original GitHub issue

The $IPFS_PATH/api file is used by a lot of developers to talk to remote nodes (learning from ipfs-companion users). T

How to improve UX for “the API defined in $IPFS_PATH/api is offline” scenario?

Perhaps like this:

IF $IPFS_PATH/api file exists and is different from the one in the config file
AND IF multiaddr inside of api file points at remote API which produces ECONNREFUSED error,
THEN ipfs-desktop should inform user about the problem with connection to remote node at {multiaddr} and display error window with built-in UI for dealing with it.

It could be a styled window similar to this mockup but with nice UI to:

(A) Change value in api file
- open file with $EDITOR or provide built-in editor directly in the error window similar to what ipfs-webui does
(B) Run ipfs repo fsck
- to remove api and potential lockfiles and try again (should be safe, technical user can always restore file by hand)
© Quit

Issue Analytics

State:
Created 5 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

hacdiascommented, Dec 9, 2018

@lidel that error might be caused by this line which will be removed as soon as the CORS PR (#738) is merged 😄 So it won’t be a problem as we won’t be testing the existence of any files.

0reactions

hacdiascommented, Feb 16, 2019

That case is already solved. I’m closing this for now since we’ve already added the necessary logic for the scenarios here described.