Already Piped Error

[sorleone]

The error I get has been around for quite long if you search for it:

https://github.com/libp2p/js-libp2p-switch/issues/235

I get it with js-ipfs version 0.31.4, 0.31.3, and 0.30.0, but I think every version has it. This is what I get:

js-ipfs/node_modules/pull-pair/index.js:11
      throw new Error('already piped')

the node crashes with varying delays, can be 15 minutes or last for much longer, it's preventing me to use IPFS.

[pgte]

I believe this is a js-ipfs issue. described here.

[sorleone]

@pgte Can I use ipfs-pubsub-room with this: https://github.com/ipfs/js-ipfs-api? If so I can get around that problem by using the go-ipfs daemon...

[pgte]

In theory if you don't use direct messages, you can, but I haven't tried.

[sorleone]

@pgte take it as feature request, support for the HTTP API would be great! Especially with private encrypted messages! However I get this error:

TypeError: this._ipfs.isOnline is not a function

Code:

const ipfsAPI = require('ipfs-api')
const Room = require('ipfs-pubsub-room')
const ipfs = ipfsAPI({host: 'localhost', port: '5001', protocol: 'http'})
const room = Room(ipfs, 'room-name')

[noxonsu]

https://github.com/ipfs/js-ipfs/issues/1446

they are wraped this error in try catch https://github.com/multiformats/js-multistream-select/pull/44