fix: proper catch-all daemon startup errors #2030
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes false-negatives when "error" is printed by
ipfs daemon
but it does not kill the process.This updated logic will set
isErrored
only whenipfs daemon
is truly unable to continue:pid
is alive, and shows "startup error" window when process is deadisErrored
state into generic "daemon startup has failed" oneCloses #2023
Closes #2018
Closes #2027
Closes #2017
Closes #2028
TODO
pid
inspectionipfs.io
is broken (butdist.ipfs.io
DNSLink still works)$IPFS_PATH/api
pointing at remote nodenull
, skippingpid
checks