Open iankressin opened 3 days ago
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.
None
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. https://github.com/iankressin/eql/blob/1579a394b73db96a96adc61ac3ec0d6c77dc9eb0/crates/core/src/interpreter/backend/resolve_account.rs#L60
get_account
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+*
Can you assign this to me @iankressin ?
Done!
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. https://github.com/iankressin/eql/blob/1579a394b73db96a96adc61ac3ec0d6c77dc9eb0/crates/core/src/interpreter/backend/resolve_account.rs#L60Additional 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+*