Closed Nuhvi closed 2 years ago
Did you update your deps? That method is in the latest minor bump of secret-stream which this module tracks.
Is there a pr we are missing for the Buffer.equals?
@mafintosh
Is there a pr we are missing for the Buffer.equals?
I meant this https://github.com/hyperswarm/hyperswarm/pull/98
to solve these:
https://github.com/hyperswarm/hyperswarm/blob/master/index.js#L181 https://github.com/hyperswarm/hyperswarm/blob/master/index.js#L231
Did you update your deps? That method is in the latest minor bump of secret-stream which this module tracks.
I made sure to update everything, but the moment I go higher than hypercore@10.0.0-alpha.25
I get the same error.
latest test, just now:
"dependencies": {
"@hyperswarm/dht": "^5.0.17",
"@hyperswarm/dht-relay": "^0.2.1",
"b4a": "^1.3.1",
"hypercore": "^10.0.0-alpha.28",
"isomorphic-ws": "^4.0.1",
"random-access-memory": "^4.0.0"
}
The relay is currently missing the changes introduced in https://github.com/hyperswarm/secret-stream/pull/10 and https://github.com/hyperswarm/secret-stream/pull/11. I'll add them ASAP.
Ah sorry, my bad
No worries! Fixed in e1b2440b3bbf8f53cacfd3f13d0e044f7abf6db4. I'm wondering if it would make sense to abstract common stream functionality like timeout and keep alive to avoid having to duplicate it for the relayed streams?
Yea totally, forgot we were "mirroring" it here.
Replicating Hypercore over a websocket relay (node or browser) fails in the case of using
hypercore@^10.0.0-alpha.26
probably because the newprotomux
?:I made sure to test up to the latest working version
hypercore@10.0.0-alpha.25
and it seems to work even with the latest versions of this package: https://github.com/Nazeh/test-hypercore-dht-relay/commit/2c9823b002ce399bca17ae6f8becd308b2f5e82apackages used:
Notice, Hyperswarm will throw an error in browser because of Buffer.equals, so you will have to manually change it in node_modules to use b4a