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

chore: fix doc typos #22984

Closed
wants to merge 1 commit into from
Closed

chore: fix doc typos #22984

wants to merge 1 commit into from

Conversation

tiendn
Copy link

@tiendn tiendn commented Dec 18, 2024

Description

Fix document typo


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 (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • 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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

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

  • Documentation

    • Updated architectural document detailing the transition to Sparse Merkle Trees for state commitments and the separation of state commitment from state storage.
    • Added sections on requirements for state storage and commitments, including functionalities for range queries and historical versioning.
  • New Features

    • Introduced new interfaces: BasicRootStore, CommitRootStore, and CacheRootStore.
    • Added new struct: RootStoreConfig.

@tiendn tiendn requested a review from a team as a code owner December 18, 2024 16:55
Copy link
Contributor

coderabbitai bot commented Dec 18, 2024

📝 Walkthrough

Walkthrough

The architectural decision record (ADR-040) proposes a significant transformation in the Cosmos SDK's state management approach. The document introduces a transition from the IAVL data structure to a Sparse Merkle Tree (SMT) for state commitments, emphasizing a clear separation between state commitment (SC) and state storage (SS). The proposed architecture aims to optimize performance by utilizing a compute-efficient structure, implementing a flexible Key-Value database approach, and refactoring the MultiStore concept into a more modular RootStore design.

Changes

File Change Summary
docs/architecture/adr-040-storage-and-smt-state-commitments.md Comprehensive update to architectural decision record describing state commitment and storage strategy
store/v2alpha1/interfaces.go Added new interfaces: BasicRootStore, CommitRootStore, CacheRootStore
store/v2alpha1/types.go Introduced new struct RootStoreConfig

Possibly related issues

Possibly related PRs

Suggested labels

Type: ADR

Suggested reviewers

  • akhilkumarpilli
  • julienrbrt
  • kocubinski

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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
Contributor

@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

🔭 Outside diff range comments (1)
docs/architecture/adr-040-storage-and-smt-state-commitments.md (1)

Line range hint 27-27: Fix broken reference link

The reference link to the IAVL node documentation is malformed.

-). The entire node is hashed, and that hash is used as the key in the underlying database, [ref](https://github.com/cosmos/iavl/blob/master/docs/node/node.md
+). The entire node is hashed, and that hash is used as the key in the underlying database, [ref](https://github.com/cosmos/iavl/blob/master/docs/node/node.md)
🧹 Nitpick comments (5)
docs/architecture/adr-040-storage-and-smt-state-commitments.md (5)

Line range hint 5-5: Update the draft date

The changelog shows a draft date of "2020-01-15" which appears outdated given the context and references in the document (e.g., Verkle Trie from 2021).

-* 2020-01-15: Draft
+* 2024-01-15: Draft

Line range hint 35-35: Fix typographical error in citation

The citation marker "[*]" is orphaned without a corresponding reference entry.

-Celestia SMT is based on Diem (called jellyfish) design [*] - it uses a compute-optimised
+Celestia SMT is based on Diem (called jellyfish) design - it uses a compute-optimised

Line range hint 35-35: Fix British English spelling

The document uses American English elsewhere, so "optimised" should be "optimized" for consistency.

-it uses a compute-optimised SMT
+it uses a compute-optimized SMT

Line range hint 196-197: Address TODO comments in types section

There are unresolved TODO comments regarding type review and caching that should be addressed before finalizing the ADR.

Would you like me to help create GitHub issues to track these TODO items?


Line range hint 246-247: Remove or complete key compression section

The key compression section is marked as TODO and needs a decision. This should either be completed or moved to a separate ADR as suggested.

Would you like me to help draft the key compression section or create a new ADR for this topic?

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4d6c991 and 6e21c1f.

📒 Files selected for processing (1)
  • docs/architecture/adr-040-storage-and-smt-state-commitments.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/architecture/adr-040-storage-and-smt-state-commitments.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🔇 Additional comments (2)
docs/architecture/adr-040-storage-and-smt-state-commitments.md (2)

282-282: ⚠️ Potential issue

Fix markdown list formatting

The reference list has an incorrect line number (282) that breaks the markdown formatting.

-* [IAVL What's Next?](https://github.com/cosmos/cosmos-sdk/issues/7100)
+* [IAVL What's Next?](https://github.com/cosmos/cosmos-sdk/issues/7100)

Likely invalid or redundant comment.


Line range hint 1-290: Verify technical accuracy of SMT implementation details

The document references Celestia's SMT implementation but should verify if the described optimizations are still current.

@julienrbrt
Copy link
Member

Note 2: At this time, we will not be accepting contributions that only fix spelling or grammar errors in documentation, code or elsewhere. The repository has a nightly job that spell checks all files and will automatically open PRs for any spelling errors.

Hey! According to our CONTRIBUTING, we do not accept single typo fix PR. Feel free to combine them in one single PR instead of opening many.

@julienrbrt julienrbrt closed this Dec 18, 2024
julienrbrt added a commit that referenced this pull request Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants