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

feat(evm): tracer option is read from the config #1922

Merged
merged 2 commits into from
Jun 11, 2024

Conversation

onikonychev
Copy link
Contributor

@onikonychev onikonychev commented Jun 11, 2024

Summary by CodeRabbit

  • New Features
    • Configuration now supports reading the tracer option for enhanced flexibility.

@onikonychev onikonychev requested a review from a team as a code owner June 11, 2024 15:38
Copy link
Contributor

coderabbitai bot commented Jun 11, 2024

Walkthrough

The recent updates enhance the NibiruApp by reading the EVM tracer option directly from the configuration. This change ensures that the tracer settings are dynamically configurable, improving the flexibility and maintainability of the application. The modifications mainly involve importing necessary packages and adjusting the InitKeepers function to utilize the configuration for the tracer option.

Changes

File Change Summary
CHANGELOG.md Documented the new feature where the tracer option is now read from the configuration.
app/keepers.go Imported appserver package and updated InitKeepers function to use appserver.EVMTracer.

Poem

In the code where tracers lie,
A change was made, oh my, oh my!
Configurations now hold the key,
To tracing paths for all to see.
With imports new and functions bright,
Nibiru soars to coding height.
🌟✨


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

@Unique-Divine
Copy link
Member

Does this close #1919?

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6511f86 and e678b7d.

Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • app/keepers.go (3 hunks)
Additional comments not posted (3)
app/keepers.go (2)

15-16: Added import for appserver "github.com/NibiruChain/nibiru/app/server".

This import is necessary for accessing the EVMTracer configuration key as used later in the InitKeepers function. Good practice to use an alias for clarity when the package name is not explicit.


406-406: Updated evmTracer initialization to use a specific configuration key.

This change enhances clarity and maintainability by using a specific configuration key from the appserver package. Please verify that EVMTracer is defined and used consistently across the codebase.

Verification successful

The search results show that EVMTracer is defined and used in multiple places across the codebase, specifically in app/server/start.go, app/server/flags.go, and app/server/config/server_config.go. This indicates that the configuration key is properly defined and utilized consistently.

  • app/server/start.go: The EVMTracer flag is defined and described.
  • app/server/flags.go: The EVMTracer constant is defined.
  • app/server/config/server_config.go: The DefaultEVMTracer is defined and used.

This confirms that the EVMTracer key is correctly integrated into the codebase.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that `EVMTracer` is defined and used correctly across the codebase.

# Test: Search for the definition and usage of `EVMTracer`. Expect: Definitions and consistent usage.
rg --type go $'EVMTracer'

Length of output: 569

CHANGELOG.md (1)

76-76: The changelog entry for PR #1922 is correctly formatted and placed under the appropriate category. Good job maintaining the changelog standards.

Copy link

codecov bot commented Jun 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.76%. Comparing base (6511f86) to head (b1d0d43).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1922      +/-   ##
==========================================
- Coverage   64.76%   64.76%   -0.01%     
==========================================
  Files         250      250              
  Lines       15963    15962       -1     
==========================================
- Hits        10339    10338       -1     
  Misses       4871     4871              
  Partials      753      753              
Files Coverage Δ
app/keepers.go 99.16% <100.00%> (-0.01%) ⬇️

@Unique-Divine Unique-Divine merged commit 4c6bb52 into main Jun 11, 2024
17 checks passed
@Unique-Divine Unique-Divine deleted the feat/evm-logs-config branch June 11, 2024 16:13
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e678b7d and b1d0d43.

Files selected for processing (1)
  • app/keepers.go (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • app/keepers.go

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.

feat: default disable the EVM logs and make it configurable
2 participants