-
Notifications
You must be signed in to change notification settings - Fork 12
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
chore: update ipfs-http-client peer dep #41
Conversation
Fixes this sort of error: ``` npm ERR! Conflicting peer dependency: [email protected] npm ERR! node_modules/ipfs-http-client npm ERR! peer ipfs-http-client@"^46.0.0" from [email protected] npm ERR! node_modules/libp2p-delegated-content-routing npm ERR! libp2p-delegated-content-routing@"^0.7.0" from the root project ```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI has some timeout failures
Ah, looks like CI has node 15 now, likely causing the failures. |
What fun: ai/nanoid#239 What's happening here is |
Should be fixed in node 15.0.1 - nodejs/node@f7abd6a |
const node = await factory.spawn({ | ||
// Lock down the nodes so testing can be deterministic | ||
ipfsOptions: { | ||
config: { | ||
Bootstrap: boostrap, | ||
Discovery: { | ||
MDNS: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MDNS is disabled already when ipfsd is passed the test: true
config option
@@ -14,20 +14,16 @@ const factory = createFactory({ | |||
ipfsHttpModule: require('ipfs-http-client'), | |||
ipfsBin: isNode ? require('go-ipfs').path() : undefined, | |||
test: true, | |||
disposable: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should really clean up after ourselves
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, ci failures are due to the recent Node 15 release, we can resolve those in a subsequent PR.
Fixes this sort of error: