-
Notifications
You must be signed in to change notification settings - Fork 445
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
feat: set and hook up libp2p-connection-manager #184
Conversation
@diasdavid I'm not sure about using |
|
@victorbjelkholm that's expected, it's not released yet and I can't do that. @diasdavid ? |
@diasdavid ping |
@pgte just released it for you and added you as an owner. I'm intrigued on why you weren't able to do it? It was the first time the module got published -- https://www.npmjs.com/package/libp2p-connection-manager. |
@diasdavid I never did ipfs or libp2p releases, it would have been the first time, so I would have needed the go-ahead. I've seen you added me as an npm owner. Thank you! |
CI is still red. Any ETA to get this ready for prime time? |
b3ec918
to
9ae1908
Compare
Updated the libp2p-connection-manager dev version, but the CI is still breaking, now with the errors: TravisCI:
Jenkins:
and others... I don't think they're related to these changes. @victorbjelkholm @diasdavid can you help? |
@pgte I rerun the tests and now they are passing. I would add a comment above the test-case, noting that it's flaky. |
9ae1908
to
d4e5721
Compare
@pgte could you describe what happens with the connection manager enabled? |
@diasdavid since the defaults impose no threshold, nothing should happen. |
This is awesome! How would someone pass connection manager options to js-ipfs to enable the limits? Do we need a PR to js-ipfs to allow it? We should also document the options in js-ipfs (or at least link to the relevant section on the connection manager repo). Also, is there something left to do on this PR? |
I think this is working, but I'd like to get some consensus around how the connection manager options are passed in. Right now, it's from |
Looks sensible to me |
Awesome. Then this should be all! :) |
@diasdavid can we get this merged? |
CI is red. Can we get it green? |
License: MIT Signed-off-by: Alan Shaw <alan@tableflip.io>
Ok so, I've fixed the merge conflict, which brings in updated dependencies. We're now getting the exact same test failures in CI that I'm seeing in master (I've logged them here also) so I think they might be unrelated to the changes in this PR. |
package.json
Outdated
"libp2p-websocket-star": "~0.8.0", | ||
"libp2p-websocket-star-rendezvous": "~0.2.3", | ||
"lodash.times": "^4.3.2", | ||
"pull-goodbye": "0.0.2", | ||
"pull-serializer": "~0.3.2", | ||
"pull-stream": "^3.6.8", | ||
"sinon": "^5.0.7", | ||
"libp2p-webrtc-star": "~0.15.0", | ||
"wrtc": "0.1.1" | ||
"wrtc": "~0.1.4" |
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.
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.
Is there a bug report open on the wrtc repo?
#194 License: MIT Signed-off-by: Alan Shaw <alan@tableflip.io>
aha, tests have now passed on Node.js 8 but fail on Node.js 10 because there's no prebuilt binary for |
## [5.0.1](libp2p/js-libp2p-websockets@v5.0.0...v5.0.1) (2022-12-08) ### Bug Fixes * cannot catch EADDRINUSE ([libp2p#198](libp2p/js-libp2p-websockets#198)) ([c7312db](libp2p/js-libp2p-websockets@c7312db)), closes [libp2p#184](libp2p/js-libp2p-websockets#184) ### Dependencies * **dev:** bump @libp2p/interface-mocks from 7.1.0 to 8.0.2 ([libp2p#199](libp2p/js-libp2p-websockets#199)) ([daff533](libp2p/js-libp2p-websockets@daff533)), closes [libp2p#318](https://github.com/libp2p/js-libp2p-websockets/issues/318) [libp2p#315](https://github.com/libp2p/js-libp2p-websockets/issues/315) [libp2p#313](https://github.com/libp2p/js-libp2p-websockets/issues/313) [libp2p#312](https://github.com/libp2p/js-libp2p-websockets/issues/312) * **dev:** bump it-all from 1.0.6 to 2.0.0 ([libp2p#193](libp2p/js-libp2p-websockets#193)) ([6213f8f](libp2p/js-libp2p-websockets@6213f8f)), closes [libp2p#28](libp2p/js-libp2p-websockets#28) [libp2p#28](libp2p/js-libp2p-websockets#28) [libp2p#27](libp2p/js-libp2p-websockets#27) [libp2p#24](libp2p/js-libp2p-websockets#24) * **dev:** bump it-drain from 1.0.5 to 2.0.0 ([libp2p#191](libp2p/js-libp2p-websockets#191)) ([e549691](libp2p/js-libp2p-websockets@e549691)), closes [libp2p#28](libp2p/js-libp2p-websockets#28) [libp2p#28](libp2p/js-libp2p-websockets#28) [libp2p#27](libp2p/js-libp2p-websockets#27) [libp2p#24](libp2p/js-libp2p-websockets#24) * **dev:** bump it-take from 1.0.2 to 2.0.0 ([libp2p#192](libp2p/js-libp2p-websockets#192)) ([4c037fc](libp2p/js-libp2p-websockets@4c037fc)), closes [libp2p#28](libp2p/js-libp2p-websockets#28)
Solves #183