You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The python substrate interface uses the websocket-client library instead of the more popular websockets. Substrate interface is written in an absolutely horrendous manner. It just does not respond to the pings, ultimately resulting in the maximum failures defined by the node and forced disconnection
How can this be solved:
Rewriting the Python substrate interface in a sane way
Forking the Polkadot SDK, as I did on a testnet, to handle the pinging in a different way
What we will do is:
Rewriting the Python substrate interface websocket communication in a sane way
The text was updated successfully, but these errors were encountered:
The root of the issue is this:
(I modified some of it for my own use, normally, this is more strict)
websockets
. Substrate interface is written in an absolutely horrendous manner. It just does not respond to the pings, ultimately resulting in the maximum failures defined by the node and forced disconnectionHow can this be solved:
What we will do is:
Rewriting the Python substrate interface websocket communication in a sane way
The text was updated successfully, but these errors were encountered: