Describe the solution you'd like
In the current implementation, if a single RPC call fails, the whole query fails. RPC request errors should be handled gracefully, returning None for the fields which the value couldn't be fetched in that query.
In the case of accounts, if one of the calls made inside the get_account method fails, should return None, instead of throwing an error.
Additional context
You can attest the current behavior in the link below, where one of the RPCs is failing to respond the request and the whole query fails.
https://eql.sh/?query=GET+*+FROM+account+vitalik.eth+ON+*
Describe the solution you'd like
In the current implementation, if a single RPC call fails, the whole query fails. RPC request errors should be handled gracefully, returning
Nonefor the fields which the value couldn't be fetched in that query.In the case of accounts, if one of the calls made inside the
get_accountmethod fails, should return None, instead of throwing an error.eql/crates/core/src/interpreter/backend/resolve_account.rs
Line 60 in 1579a39
Additional context
You can attest the current behavior in the link below, where one of the RPCs is failing to respond the request and the whole query fails.
https://eql.sh/?query=GET+*+FROM+account+vitalik.eth+ON+*