Igor Artamonov

Sorry, I missed your response. As we both see, there're few different ways to have such external calls, and one proposed by me is more complex. At this moment it's...

Hi, thank you for the finding. There was a severe bug in the WS code, which I had fixed recently (not release yet). But this one may be unrelated. I'm...

I just published version 0.8.2, please try it. Not sure about this issue though, but if fixed couple of other issues you reported.

Ok, thanks. Just looked at the stacktrace, it seems to be more complex that I thought. It happens inside WS codec implementation (`WebSocketClientHandshaker13`), not even Dshackle. I guess I'll need...

I'm just not sure when I can focus on this bug. I guess it's not high priority, because it can continue with HTTP RPC, right? I can take a look...

Kind of good news :) The main purpose to use WS for Dshackle is to subscribe to the new blocks (`newHeads`), hope they'll add it

You're right, it probably makes sense to use WebSocket for all requests. It relies on HTTP only because of the historical reasons, was easier to start/debug/etc. Hope to change it...

Dshackle tries to query 3 nodes (when available) to ensure consistency, and it seems it doesn't works well with Matic. Because Dshackle checks only fully synced nodes for nonce (also...

Hi @kaeptnb, thank you for reporting it. Is it possible to catch the traffic sample for such request from Chainlink? Like with Wireshark or similar. I'd like to see what...

I didn't figure out what is the reason because the log looks like a normal interaction. But I've made several other improvements and fixes to Websocket since the last release,...