chore: cleanup and test nodedb logic

[aljo242]

add tests for the Committing logic in nodedb.

clean up and organize file a bit

Summary by CodeRabbit

• Refactor

  • Improved naming consistency and code style for better readability.
  • Replaced hardcoded values with named constants for clarity.
  • Enhanced error handling and error comparison methods.

• Bug Fixes

  • Corrected typos in comments and variable names.

• Tests

  • Added new tests to verify synchronization and pruning behavior during commit operations.

• Chores

  • Removed unused constants and made minor documentation improvements.

[coderabbitai[bot]]

Walkthrough

This update introduces a new test file for the nodeDB commit and pruning synchronization logic, applies multiple refactorings and style improvements to nodedb.go, and corrects minor typos in comments. Changes include renaming types and variables for clarity, improved error handling, and more idiomatic Go code, without altering core logic.

Changes

File(s)	Change Summary
mutable_tree.go	Fixed a typo in a comment ("rigthNode" → "rightNode").
nodedb.go	Refactored key prefix constants, renamed types/variables for clarity, introduced ErrNodeMissingNodeKey, improved error handling, and made style/idiomatic Go changes. No logic changes.
nodedb_commit_test.go	Added new test file with unit tests for nodeDB commit/pruning synchronization, blocking, and signaling behavior.

Sequence Diagram(s)

sequenceDiagram
    participant Test as Test Suite
    participant NodeDB as nodeDB
    participant Pruning as Pruning Operation

    Test->>NodeDB: SetCommitting()
    Test->>Pruning: Start deleteFromPruning() in goroutine
    Pruning-->>NodeDB: Waits (blocked) if committing
    Test->>NodeDB: UnsetCommitting()
    NodeDB-->>Pruning: Signals unblock
    Pruning-->>Test: Completes operation

Possibly related PRs

• cosmos/iavl#1015: Refactors error variable declaration to use errors.New for ErrNodeMissingNodeKey, directly related to similar error handling changes in this PR.

Poem

In the warren of code, a hop and a sweep,
Typo fixed, constants named, roots run deep.
Tests now ensure our pruning waits right,
While commits burrow on through the night.
A nibble of clarity, a byte of delight—
The garden of IAVL grows ever more bright!
🥕

[!WARNING] There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (1.64.8)

Error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2 Failed executing command with error: you are using a configuration file for golangci-lint v2 with golangci-lint v1: please use golangci-lint v2

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f05dd3a6fc8e345e18bc009834952b04f24d1826 and 6807998af1dd9a2573baa2649de79457e3e31d9f.

📒 Files selected for processing (3)

• mutable_tree.go (1 hunks)
• nodedb.go (20 hunks)
• nodedb_commit_test.go (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (2)

nodedb_commit_test.go (2)

db/memdb.go (1)

• NewMemDB (55-60)

options.go (1)

• DefaultOptions (95-97)

nodedb.go (7)

keyformat/prefix_formatter.go (1)

• NewFastPrefixFormatter (14-16)

keyformat/key_format.go (1)

• NewKeyFormat (36-51)

cache/cache.go (2)

• New (55-61)
• Node (10-12)

node.go (1)

• Node (59-75)

v2/node.go (1)

• Node (50-65)

fastnode/fast_node.go (1)

• Node (15-19)

mutable_tree.go (1)

• ErrVersionDoesNotExist (18-18)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Benchmarks
• GitHub Check: Analyze (go)
• GitHub Check: Test

🔇 Additional comments (27)

mutable_tree.go (1)

1033-1033: LGTM! Clean typo fix.

The comment typo correction improves code documentation quality without affecting functionality.

nodedb_commit_test.go (6)

12-16: Well-structured test helper function.

The setupNodeDB helper function follows good testing practices by using t.Helper() and providing a clean nodeDB instance for tests.

---

18-35: Comprehensive basic flag testing.

This test effectively verifies the basic committing flag functionality and channel signaling behavior. The timeout-based channel testing approach is appropriate for ensuring signal delivery.

---

37-65: Excellent signal timing verification.

This test properly validates that the channel signal is only released when UnsetCommitting() is called, not before. The use of goroutines and timeout-based verification ensures proper synchronization behavior.

---

67-95: Robust pruning synchronization test.

This test correctly verifies that deleteFromPruning blocks during commit operations and resumes afterward. The goroutine-based approach with timeout verification is well-implemented.

---

97-132: Thorough save operation blocking test.

The test properly validates that saveNodeFromPruning operations are blocked during commits. The Node creation with realistic field values adds good test coverage.

---

134-167: Excellent concurrent access validation.

This test effectively simulates real-world concurrent commit and pruning scenarios. The timing assertions and sync.WaitGroup usage demonstrate proper understanding of the synchronization requirements.

nodedb.go (20)

40-46: Excellent refactoring: hardcoded literals to named constants.

Converting hardcoded byte literals to named constants significantly improves code readability and maintainability. The constant names are descriptive and follow Go naming conventions.

---

51-51: Improved comment clarity.

The enhanced comment better explains the purpose and structure of the nodeKeyFormat, making the code more self-documenting.

---

54-54: Good documentation improvement.

Adding this clarifying comment helps developers understand the specific use case for this format.

---

58-61: Enhanced documentation for fast key format.

The expanded comment provides valuable context about the fast query mechanism and its relationship to tree versions, improving code comprehensibility.

---

78-82: Well-structured error handling improvement.

Introducing the exported ErrNodeMissingNodeKey error improves error handling consistency and provides better error identification for callers. The error message is clear and descriptive.

---

161-161: Improved variable naming for clarity.

Using isLegacyNode instead of checking length directly makes the code more self-documenting and easier to understand.

---

172-185: Enhanced error handling and logic flow.

The improved conditional structure with isLegacyNode variable makes the logic clearer and easier to follow, while maintaining the same functionality.

---

429-435: Excellent naming consistency improvement.

Renaming rootkeyCache to rootKeyCache follows Go naming conventions for consistent capitalization in compound words. This improves code readability and maintains consistency with other identifiers.

---

437-451: Consistent method renaming.

The method signature update maintains consistency with the renamed struct type while preserving all functionality.

---

460-466: Clean constructor naming update.

The constructor function naming follows the same consistency improvements as the struct and methods.

---

470-470: Consistent parameter type update.

The parameter type update maintains consistency with the renamed cache type throughout the codebase.

---

481-481: Method call consistency maintained.

The method call updates maintain consistency with the renamed methods while preserving functionality.

---

646-646: Improved comment clarity.

The refined comment better explains the reasoning behind not touching fast node indexes during version deletion operations.

---

751-751: Improved cache instantiation strategy.

Creating a new rootKeyCache instance for each version deletion operation is a good practice that prevents potential cache pollution between different version operations, improving reliability.

---

1167-1167: Consistent function call update.

The function call update maintains consistency with the new cache instantiation pattern.

---

1170-1170: Parameter type consistency maintained.

The parameter type update ensures consistency throughout the refactored codebase.

---

1243-1259: Improved variable declarations.

Using more explicit variable declarations (var leaves []*Node instead of implicit declarations) improves code clarity and follows Go best practices.

---

1352-1352: Enhanced function documentation.

The improved comment provides better context about the function's purpose and behavior, including details about the exclusive end version parameter.

---

1372-1372: Proper error handling pattern.

Using errors.Is() for error comparison is the recommended Go practice and provides more robust error handling than direct equality checks.

---

1410-1410: Proper error handling in string formatting.

Using the blank identifier _ for the error return from fmt.Fprintf is appropriate here since writing to a buffer shouldn't fail, and this follows Go conventions for intentionally ignored return values.

✨ Finishing Touches

• [ ] 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

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.

[aljo242]

@Mergifyio backport release/v1.2.x

[aljo242]

@Mergifyio backport release/v1.3.x

[mergify[bot]]

backport release/v1.2.x

🟠 Waiting for conditions to match

• [ ] merged [📌 backport requirement]

[mergify[bot]]

backport release/v1.3.x

🟠 Waiting for conditions to match

• [ ] merged [📌 backport requirement]