-
Notifications
You must be signed in to change notification settings - Fork 251
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
Implement BlockCache trait for FsBlockDb #1535
base: main
Are you sure you want to change the base?
Implement BlockCache trait for FsBlockDb #1535
Conversation
e0d5339
to
4995d68
Compare
4995d68
to
c91dc38
Compare
Rebased on I'm going to perform more rebases on this to clean up the commit history and break apart the larger changes as best I can, to make the PR easier to review and potentially break out smaller pieces of it into separate PRs. |
c91dc38
to
1675bf3
Compare
Rebased on |
1675bf3
to
2c32c73
Compare
Force-pushed to refactor the commits without any changes. In particular, I've pulled most of the I also plan to rebase this PR again once #1595 merges, to move away from the |
The `BlockCache::truncate` default method is removed because the `trait-variant` crate does not yet support default methods.
2c32c73
to
890fd86
Compare
Rebased on The main next thing I want to figure out is whether the current state of the first commit can be paired down even further. |
Instead of requiring `zcash_client_backend::data_api::chain::Error`, it now works with any error type that `BlockSource::Error` can be converted into. We require an explicit conversion function instead of using `From` because in the specific case of `data_api::chain::Error` it would result in conflicting `From` impls.
…ache trait Co-authored-by: Jack Grigg <[email protected]>
890fd86
to
020438c
Compare
Force-pushed to remove the dependency of |
BlockCache::read
for BlockDb, neccessary for callingscan_cached_blocks