-
Notifications
You must be signed in to change notification settings - Fork 202
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
Conversation
WalkthroughThe recent updates enhance the Changes
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
Does this close #1919? |
There was a problem hiding this 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
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 forappserver "github.com/NibiruChain/nibiru/app/server"
.This import is necessary for accessing the
EVMTracer
configuration key as used later in theInitKeepers
function. Good practice to use an alias for clarity when the package name is not explicit.
406-406
: UpdatedevmTracer
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 thatEVMTracer
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 inapp/server/start.go
,app/server/flags.go
, andapp/server/config/server_config.go
. This indicates that the configuration key is properly defined and utilized consistently.
app/server/start.go
: TheEVMTracer
flag is defined and described.app/server/flags.go
: TheEVMTracer
constant is defined.app/server/config/server_config.go
: TheDefaultEVMTracer
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.
Codecov ReportAll modified and coverable lines are covered by tests ✅
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
|
There was a problem hiding this 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
Summary by CodeRabbit