Skip to content
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

use custom cache store to properly implement interfaces #46

Merged
merged 4 commits into from
Aug 20, 2024

Conversation

beer-1
Copy link
Collaborator

@beer-1 beer-1 commented Aug 20, 2024

Description

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Introduced a new CacheStore type for efficient data caching, improving data retrieval performance.
  • Refactor

    • Simplified context management in database operations for better alignment with SDK best practices.
    • Streamlined usage and instantiation of CacheStore by removing unnecessary dependencies.
    • Improved JSON encoding and decoding methods for better maintainability and testing.
  • Bug Fixes

    • Enhanced clarity and robustness in transaction handling and error management.
  • Tests

    • Added comprehensive unit tests for the CacheStore functionality, validating core operations like key existence, setting, and deletion.

@beer-1 beer-1 requested a review from a team as a code owner August 20, 2024 04:21
@beer-1 beer-1 self-assigned this Aug 20, 2024
Copy link

coderabbitai bot commented Aug 20, 2024

Walkthrough

The recent changes enhance the project's caching capabilities by directly incorporating github.com/allegro/bigcache/v3. Refactoring in EVMIndexerImpl improves database context management and simplifies transaction handling. A new CacheStore type is introduced for efficient data retrieval, while JSON encoding and decoding methods are modernized for better maintainability. Overall, these updates aim to boost performance, clarity, and robustness across the codebase.

Changes

Files Change Summary
go.mod Added direct dependency on github.com/allegro/bigcache/v3 at version v3.1.0, removing it from indirect dependencies.
indexer/abci.go, indexer/indexer.go Refactored context management in ListenFinalizeBlock, removed batch for simpler transaction handling, and updated CacheStore references to eliminate the store package.
indexer/store.go Introduced new CacheStore type implementing corestoretypes.KVStore, including methods for efficient caching and data retrieval.
indexer/utils.go Updated collJsonVal methods for JSON encoding/decoding to utilize new EncodeJSON and DecodeJSON methods.
indexer/store_test.go Added comprehensive unit tests for CacheStore, validating key existence checks, setting, and deleting keys.
indexer/utils_test.go Introduced Test_collJsonVal to validate encoding and decoding of a struct using collJsonVal.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EVMIndexerImpl
    participant CacheStore
    participant DB

    User->>EVMIndexerImpl: Request data
    EVMIndexerImpl->>CacheStore: Check cache for data
    alt Data exists in cache
        CacheStore-->>EVMIndexerImpl: Return cached data
    else Data not in cache
        EVMIndexerImpl->>DB: Fetch data from database
        DB-->>EVMIndexerImpl: Return data
        EVMIndexerImpl->>CacheStore: Store data in cache
        CacheStore-->>EVMIndexerImpl: Confirm storage
    end
    EVMIndexerImpl-->>User: Provide data
Loading

Poem

🐰 In the realm of code, a change took flight,
Caching and context, oh what a sight!
With bigcache now, the data flows free,
Simplified paths for you and me.
Hooray for the rabbit, the code's delight,
Hop on, dear friend, let’s code through the night! 🌙


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Aug 20, 2024

Codecov Report

Attention: Patch coverage is 61.84211% with 29 lines in your changes missing coverage. Please review.

Project coverage is 26.54%. Comparing base (e9acda2) to head (bd60f1c).
Report is 1 commits behind head on main.

Files Patch % Lines
indexer/store.go 69.23% 17 Missing and 3 partials ⚠️
indexer/abci.go 0.00% 8 Missing ⚠️
indexer/indexer.go 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
+ Coverage   26.19%   26.54%   +0.34%     
==========================================
  Files         110      111       +1     
  Lines       11707    11766      +59     
==========================================
+ Hits         3067     3123      +56     
  Misses       8198     8198              
- Partials      442      445       +3     
Files Coverage Δ
indexer/utils.go 18.60% <100.00%> (+12.98%) ⬆️
indexer/indexer.go 0.00% <0.00%> (ø)
indexer/abci.go 0.00% <0.00%> (ø)
indexer/store.go 69.23% <69.23%> (ø)

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 11

Outside diff range, codebase verification and nitpick comments (1)
indexer/abci.go (1)

Line range hint 33-185: Add test coverage for ListenFinalizeBlock.

The ListenFinalizeBlock method now uses sdkCtx, but there is no test coverage for this change. Ensure that tests are added to verify the context management and database operations.

Would you like me to help create unit tests for this method or open a GitHub issue to track this task?

Tools
GitHub Check: codecov/patch

[warning] 147-147: indexer/abci.go#L147
Added line #L147 was not covered by tests


[warning] 151-151: indexer/abci.go#L151
Added line #L151 was not covered by tests


[warning] 157-157: indexer/abci.go#L157
Added line #L157 was not covered by tests

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e9acda2 and 0a49836.

Files selected for processing (5)
  • go.mod (2 hunks)
  • indexer/abci.go (4 hunks)
  • indexer/indexer.go (3 hunks)
  • indexer/store.go (1 hunks)
  • indexer/utils.go (1 hunks)
Additional context used
GitHub Check: codecov/patch
indexer/utils.go

[warning] 83-83: indexer/utils.go#L83
Added line #L83 was not covered by tests


[warning] 87-87: indexer/utils.go#L87
Added line #L87 was not covered by tests

indexer/store.go

[warning] 20-28: indexer/store.go#L20-L28
Added lines #L20 - L28 were not covered by tests


[warning] 31-34: indexer/store.go#L31-L34
Added lines #L31 - L34 were not covered by tests


[warning] 38-43: indexer/store.go#L38-L43
Added lines #L38 - L43 were not covered by tests


[warning] 46-49: indexer/store.go#L46-L49
Added lines #L46 - L49 were not covered by tests


[warning] 52-54: indexer/store.go#L52-L54
Added lines #L52 - L54 were not covered by tests


[warning] 58-62: indexer/store.go#L58-L62
Added lines #L58 - L62 were not covered by tests


[warning] 64-67: indexer/store.go#L64-L67
Added lines #L64 - L67 were not covered by tests


[warning] 70-72: indexer/store.go#L70-L72
Added lines #L70 - L72 were not covered by tests


[warning] 76-86: indexer/store.go#L76-L86
Added lines #L76 - L86 were not covered by tests


[warning] 90-99: indexer/store.go#L90-L99
Added lines #L90 - L99 were not covered by tests


[warning] 108-109: indexer/store.go#L108-L109
Added lines #L108 - L109 were not covered by tests


[warning] 117-118: indexer/store.go#L117-L118
Added lines #L117 - L118 were not covered by tests


[warning] 121-122: indexer/store.go#L121-L122
Added lines #L121 - L122 were not covered by tests

indexer/indexer.go

[warning] 85-85: indexer/indexer.go#L85
Added line #L85 was not covered by tests

indexer/abci.go

[warning] 33-33: indexer/abci.go#L33
Added line #L33 was not covered by tests


[warning] 67-67: indexer/abci.go#L67
Added line #L67 was not covered by tests


[warning] 71-71: indexer/abci.go#L71
Added line #L71 was not covered by tests


[warning] 147-147: indexer/abci.go#L147
Added line #L147 was not covered by tests


[warning] 151-151: indexer/abci.go#L151
Added line #L151 was not covered by tests


[warning] 157-157: indexer/abci.go#L157
Added line #L157 was not covered by tests


[warning] 181-181: indexer/abci.go#L181
Added line #L181 was not covered by tests


[warning] 185-185: indexer/abci.go#L185
Added line #L185 was not covered by tests

Additional comments not posted (1)
go.mod (1)

18-18: Dependency change approved. Verify bigcache usage in the codebase.

The change from an indirect to a direct dependency for github.com/allegro/bigcache/v3 is consistent with the PR's objective to implement a custom cache store. Ensure that all usages of this package are correctly implemented and documented.

Verification successful

Verification successful: bigcache usage is consistent and properly implemented.

The bigcache library is directly used in indexer/store.go within the CacheStore struct and its initialization. The implementation aligns with the dependency change in go.mod. Ensure that this usage is documented if necessary.

  • File: indexer/store.go
  • Key Usages:
    • CacheStore struct with *bigcache.BigCache
    • Initialization with bigcache.New
    • Error handling for bigcache.ErrEntryNotFound
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `bigcache` in the codebase.

# Test: Search for the `bigcache` usage. Expect: Proper implementation and documentation.
rg --type go -A 5 'bigcache'

Length of output: 1153

indexer/utils.go Show resolved Hide resolved
indexer/utils.go Show resolved Hide resolved
indexer/store.go Show resolved Hide resolved
Comment on lines +31 to +34
return &CacheStore{
store: cachekv.NewStore(store),
cache: cache,
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add test coverage for NewCacheStore.

The NewCacheStore function initializes a new cache store, but there is no test coverage for this functionality. Ensure that tests are added to verify the initialization process.

Would you like me to help create unit tests for this function or open a GitHub issue to track this task?

Tools
GitHub Check: codecov/patch

[warning] 31-34: indexer/store.go#L31-L34
Added lines #L31 - L34 were not covered by tests

indexer/store.go Show resolved Hide resolved
indexer/store.go Show resolved Hide resolved
indexer/store.go Show resolved Hide resolved
indexer/store.go Show resolved Hide resolved
indexer/store.go Show resolved Hide resolved
indexer/indexer.go Show resolved Hide resolved
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0a49836 and bd60f1c.

Files selected for processing (2)
  • indexer/store_test.go (1 hunks)
  • indexer/utils_test.go (1 hunks)
Additional comments not posted (3)
indexer/store_test.go (1)

11-49: Comprehensive test coverage for CacheStore.

The test function Test_StoreIO effectively covers the basic CRUD operations for the CacheStore. The use of require assertions ensures that errors are properly handled and expected values are verified.

indexer/utils_test.go (2)

Line range hint 10-37: Effective validation of data unpacking.

The test function Test_UnpackData accurately validates the serialization and deserialization of MsgCreateResponse. The use of require assertions ensures that errors are caught and the data integrity is maintained.


39-58: Successful test of JSON codec functionality.

The test function Test_collJsonVal effectively validates the encoding and decoding of a struct using a generic JSON codec. The assertions ensure that the JSON representation is correct and that the struct is accurately reconstructed.

@beer-1 beer-1 merged commit 41c1c3e into main Aug 20, 2024
8 checks passed
@beer-1 beer-1 deleted the feat/cache-store branch August 20, 2024 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants