Blaž Hrastnik

@fishcakez we're running into similar issues. Aurora initiates a failover, and when that happens they actually restart all the nodes -- we get ~16 errors ``` Elixir.Mariaex.Errorlib/ecto/adapters/sql.ex:440 [tcp] `recv` failed...

We'll experiment turning off DNS caching on the erlang level; there's a `cache_refresh` flag -- although the default is 1 hour, and our nodes have been running for days, it...

In that case, if OS's DNS was used, why would rebooting the application (and not the whole node) fix the problem? Maybe the reconnect is faster than the AWS failover

Looks like this was fixed? Works correctly for me on the linked page

Most RPC calls also have issues: they return pointers which could be deserialized to `nil`. For example https://github.com/gagliardetto/solana-go/blob/7de08b22f3afd588a275212aff05fa5f2580f356/rpc/getBalance.go#L25-L34 could return `GetBalanceResult` rather than `*GetBalanceResult`?

https://github.com/linux-surface/linux-surface/wiki/Surface-Laptop-2

https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup#touch-controls

We are only using the RPC client, not the RPC server. Our node will use Juno/Caigo to send transactions onto the network: https://github.com/smartcontractkit/chainlink-starknet/tree/develop/pkg/starknet

So we don't need an server with an embedded database, just a straightforward RPC client. `mdbx` is adding additional build constraints to our build process which might be a problem...

No rush! Just wanted to raise the issue early enough while you're still working on the RPC package. I think it would make sense to split out the types and...