-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Node crashes with "Missing peerId" after a few minutes #1221
Comments
I have seen the same thing |
Pinpointed it at MetaMask/mesh-testing#3 (comment) |
I want to get some tests added to validate and maintain integrity, but I believe this issue was fixed by the connection cascading fix in libp2p/js-libp2p-secio#98. This was included in the js-ipfs 0.28.0 release. |
My initial thought was wrong, I found the issue causing the crash. libp2p/js-libp2p-secio#101 resolves this Once that's merged and added to a release, I will make a PR here to bump the secio version. |
This was accidentally closed. I'll have a PR shortly to update versioning to properly fix this. |
I am still getting this issue while using ipfs-js 0.28.2 and am unable to be discoverable and have peers. Anyone else having this issue as well? |
@shessenauer Are you using webrtc or websocket as discovery? Webrtc is still resource heavy and bit new still compared to the more stable websocket. |
@kevinsimper currently using websocket as discovery |
@shessenauer Then you need to post an example of what is not working :) |
* test: adds tests for metadata with mfs stat and files.add * chore: remove gh url
0.27.7
x86_64 GNU/Linux
Type:
Bug
Description:
Node crashes after ~5 minutes (varies though) with error
AssertionError [ERR_ASSERTION]: Missing peerId. Use Peer.create(cb) to create one
Full logs are here: https://gist.github.com/VictorBjelkholm/0e7819b3a19caab7dbfc3172ab222184
Steps to reproduce the error:
git clone https://github.com/VictorBjelkholm/js-ipfs-docker.git
cd js-ipfs-docker
yarn
node index.js
The text was updated successfully, but these errors were encountered: