Fix some places where devnet was not using in-mem dbs

[joshklop]

Summary by CodeRabbit

• New Features

  • Integration of the Monomer node into the server structure.
  • Enhanced configurability for the Monomer command with additional flags.

• Bug Fixes

  • Improved error handling during the node startup process for better logging and context.

• Refactor

  • Adjusted logic for starting the application and handling the database backend based on the environment.
  • Refined service registration logic for the Monomer node.

[coderabbitai]

Walkthrough

The changes in this pull request focus on integrating the Monomer node into the existing server structure within the integrations/integrations.go file. Key modifications include the addition of a new import statement, updates to the AddMonomerCommand function for enhanced configurability, and adjustments to the startCommandHandler and startInProcess functions to enforce new operational logic. The refactoring of database handling and significant modifications to the startMonomerNode function aim to improve error handling and service registration during the node startup process.

Changes

File Path	Change Summary
integrations/integrations.go	- Added import for github.com/ethereum/go-ethereum/ethdb. - Updated AddMonomerCommand with additional flags. - Modified startCommandHandler to enforce inProcessConsensus. - Adjusted logic in startInProcess for Monomer node initiation. - Refactored database handling for memory or Pebble database. - Significant changes in startMonomerNode for listener setup and error handling.

Possibly related PRs

• Add keplr integration for L2 devnet chain #246: This PR enhances the Monomer project by exposing the Cosmos gRPC and API servers when a Monomer node is initiated, which is directly related to the changes made in the main PR regarding the integration of the Monomer node and its server functionalities.
• Devnet runs only in-memory #257: This PR modifies the integrations/integrations.go file to improve the handling of development configurations for the Monomer node, which aligns with the main PR's focus on enhancing the Monomer node's startup process and configuration management.

Suggested reviewers

• natebeauregard

Poem

In the garden of code, a Monomer blooms,
With flags flying high, dispelling the glooms.
From CometBFT to a new node's embrace,
We weave through the logic, a dance in this space.
Errors now logged, with context so clear,
A rabbit hops forth, with a joyful cheer! 🐇✨

---

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

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

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0f167ef and 3304cfb.

📒 Files selected for processing (1)

• integrations/integrations.go (3 hunks)

🔇 Additional comments (1)

integrations/integrations.go (1)

37-37: Import statement for ethdb added

The import of github.com/ethereum/go-ethereum/ethdb is necessary for handling the ethdb.Database interface used later in the code.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3304cfb and 75e9290.

📒 Files selected for processing (1)

• integrations/integrations.go (3 hunks)

🔇 Additional comments (4)

integrations/integrations.go (4)

37-37: LGTM!

The new import is correctly placed and necessary for the database interface changes.

---

324-326: Consider using local configuration instead of modifying global Viper.

This comment was previously raised and is still valid. Modifying the global Viper instance directly may have unintended side effects on other parts of the application.

---

456-470: LGTM! Database implementation looks solid.

The implementation correctly handles both in-memory and persistent database cases with proper error handling and path construction.

---

468-470: LGTM! Error handling is well-implemented.

The error handling is comprehensive with proper error wrapping and descriptive messages.