Kevin Chia
Kevin Chia
+1. Is there any update on this one?
@FredericBriolet I turned out to use webpack instead.
cc @pipermerriam @carver @hwwhww @ChihChengLiang
@carver That sounds great! Thank you for answering:)
Is there any update on this? Though I can see [why](https://github.com/eth-brownie/brownie/blob/3aecd87f47c9c316c85b0b0c6252ff7d900cca74/brownie/network/transaction.py#L15) `black` is put in `requirements.in` instead of `requirements-dev.in`.
Just an update on our end: my colleague found this line failed https://github.com/najamelan/ws_stream_wasm/blob/4035d4657388040938f22829fef2628c1243bbfa/src/ws_stream.rs#L314 If the line is replaced by ```rust WsMessage::Binary(d) => { let buffer = ArrayBuffer::new( d.len() .try_into() .expect("Message...
It's pretty nice to me. If there are too many combinations of the flags in a namespace, does it make sense to have something like `-tpt="tcp,ws"`, and the argument parser...
Thanks a lot to @raulk for all information in the call. It seems a good start from implementing the bindings to `go-libp2p-daemon`, and I will start trying it from Python...
Sorry for the late update. After re-examination of our code, it seems the operations of `host.Host`(including `Peerstore` and `Swarm`), DHT, and pubsub cover most of our requirements. Unless we have...
I guess it's because the daemon can use unix domain socket as well as the tcp socket. A multiaddress can represent both protocols.