chore: smaller dep updates #1959
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lidel
force-pushed
the
chore/patch-updates
branch
from
d268dd0 to
3eedd0b
Compare
This fixes regression introduced by #1899
lidel
commented
Jan 21, 2022
| @@ -79,7 +79,7 @@ module.exports = async function (opts) { | |||
| logger.info(`[daemon] PeerID is ${id}`) | |||
| logger.info(`[daemon] Repo is at ${ipfsd.path}`) | |||
| } catch (err) { | |||
| if (!err.message.includes('ECONNREFUSED') || !err.message.includes('ERR_CONNECTION_REFUSED')) { | |||
| if (!err.message.includes('ECONNREFUSED') && !err.message.includes('ERR_CONNECTION_REFUSED')) { | |||
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 bumps another set of dependencies. (part of release prep)
TODO
npm startinitializes a new repo (2) quit (3)npm startfails to start daemon correctly, webui is displayed in offline state~/.ipfs/apiaround.[daemon] removing api fileworked fine (after confirming that multiaddr inapiis from the local daemon who is offline, and not a remote node) – I suspect addingERR_CONNECTION_REFUSEDcheck introduced a bug, probably invalid condition