fix: app-db-backend not recognized on prune command

[helder-moreira]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces three primary changes. A new entry has been added to the "Unreleased" section in the changelog documenting a bug fix for the app database backend during the prune command. The command registration in the CLI has been updated to use a new function signature that accepts an additional parameter, altering how the pruning command is initialized. Additionally, the dependency version for the Cosmos SDK in the go.mod file has been updated from version v0.47.11-nibiru.2 to v0.47.11-nibiru.3.

Changes

File(s)	Change Summary
CHANGELOG.md	Added new unreleased entry documenting bug fix: "app-db-backend not recognized on prune command" (#2217).
cmd/.../root.go	Updated pruning command registration: replaced pruning.PruningCmd(a.newApp) with pruning.Cmd(a.newApp, app.DefaultNodeHome), reflecting a signature update.
go.mod	Updated dependency: Changed github.com/cosmos/cosmos-sdk version from v0.47.11-nibiru.2 to v0.47.11-nibiru.3.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant R as RootCmd
    participant P as Pruning Module
    participant A as App Module

    U->>R: Execute prune command
    R->>P: Call Cmd(a.newApp, app.DefaultNodeHome)
    P->>A: Initialize pruning with new parameters
    A-->>P: Return application configuration
    P-->>R: Signal command execution result
    R-->>U: Deliver prune operation outcome

Loading

Suggested reviewers

• Unique-Divine
• k-yang

Poem

Oh, what a hop, a skip, a bound,
Changes in the code all around,
A new line in the changelog’s tale,
Commands refined, no detail stale,
I, the rabbit, cheer the fix so sound!
🐇✨ hopped into progress without a frown!

---

📜 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 a85cbc8 and eac3bd1.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• CHANGELOG.md (1 hunks)
• cmd/nibid/cmd/root.go (1 hunks)
• go.mod (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• go.mod

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

• GitHub Check: integration-tests

🔇 Additional comments (2)

CHANGELOG.md (1)

54-54: LGTM!

The changelog entry follows the standard format and clearly describes the bug fix.

cmd/nibid/cmd/root.go (1)

118-118: LGTM! The change fixes the app-db-backend recognition issue.

The update to include app.DefaultNodeHome in the pruning command registration ensures that the command can correctly locate and manage the application's database backend.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 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.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.47%. Comparing base (a85cbc8) to head (eac3bd1).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2217   +/-   ##
=======================================
  Coverage   64.47%   64.47%           
=======================================
  Files         276      276           
  Lines       22390    22390           
=======================================
  Hits        14436    14436           
  Misses       6969     6969           
  Partials      985      985           

Files with missing lines	Coverage Δ
cmd/nibid/cmd/root.go	78.28% <100.00%> (ø)