-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve eth_getLogs performance for latest block #6305
Improve eth_getLogs performance for latest block #6305
Conversation
false, | ||
); | ||
} | ||
return Ok(all_logs); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey!
small nit: I think that the idiomatic way in Rust and across the repo is not to add ";" in return statements
maybe you have some auto-fmt tooling that put ";" after returns
I got such problems a few times in my rust setup
Try to use "cargo +nightly fmt" , it helps!
ps
cargo clippy --bin "reth" --workspace --features "ethereum" --lib --tests --benches --examples
and this one to check lints
@leontiad thanks for taking the time here! what's missing for us to take a look? |
ah my bad, this one slipped through going over this asap |
I am having an issue with http::test_call_filter_functions_http test |
Overall thank you for the support ! As a generic comment as a first contributor I was confused on what local tests/fmt/clippy I need to run before pushing and open the PR. Unless I miss it and is already there a one command line unifying all clippy/formatter/tests would really help. |
you can actually run |
thanks, I need some help with a failing test. Can someone have a look @mattsse |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very sorry for the delayed review here -.-
this is going in the right direction and is pretty close.
I only have one suggestion to get rid of the block_hash and latest lookup, by reusing the previously fetched ChainInfo
object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
tysm!
🚀 🚀 🚀 |
Solves #5680