Skip to content

refactor(cmd/evm,eth/tracers): refactor structlogger and make it streaming #30806 #33227#2286

Open
gzliudan wants to merge 1 commit intoXinFinOrg:dev-upgradefrom
gzliudan:fix_structlogger
Open

refactor(cmd/evm,eth/tracers): refactor structlogger and make it streaming #30806 #33227#2286
gzliudan wants to merge 1 commit intoXinFinOrg:dev-upgradefrom
gzliudan:fix_structlogger

Conversation

@gzliudan
Copy link
Copy Markdown
Collaborator

@gzliudan gzliudan commented Apr 8, 2026

Proposed changes

Refactor StructLogger so it can either buffer legacy trace results for RPC responses or stream formatted output directly to the CLI.

Switch cmd/evm debug tracing to the streaming path and keep debug.traceCall on the buffered path so it can still return structured trace results.

Update the tracer benchmark and related tests to match the new hook-based logger lifecycle and the raw JSON structLogs representation.

Treat the struct logger limit as a response-size bound in bytes instead of counting collected trace entries.

Ref:

Types of changes

What types of changes does your code introduce to XDC network?
Put an in the boxes that apply

  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Changes that don't change source code or tests
  • docs: Documentation only changes
  • feat: A new feature
  • fix: A bug fix
  • perf: A code change that improves performance
  • refactor: A code change that neither fixes a bug nor adds a feature
  • revert: Revert something
  • style: Changes that do not affect the meaning of the code
  • test: Adding missing tests or correcting existing tests

Impacted Components

Which parts of the codebase does this PR touch?
Put an in the boxes that apply

  • Consensus
  • Account
  • Network
  • Geth
  • Smart Contract
  • External components
  • Not sure (Please specify below)

Checklist

Put an in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

  • This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
  • Tested on a private network from the genesis block and monitored the chain operating correctly for multiple epochs.
  • Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
  • Tested the backwards compatibility.
  • Tested with XDC nodes running this version co-exist with those running the previous version.
  • Relevant documentation has been updated as part of this PR
  • N/A

Copilot AI review requested due to automatic review settings April 8, 2026 06:55
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 8, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cdbc8f41-3ceb-4504-b2dc-9d06f144059f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Refactors StructLogger to support either buffering legacy RPC trace results or streaming formatted opcode traces directly to CLI output.

Changes:

  • Added streaming mode to StructLogger and switched buffered mode to store pre-encoded legacy structLogs JSON entries ([]json.RawMessage).
  • Updated cmd/evm run --debug to use the streaming struct logger path and moved VM log pretty-printing into cmd/evm.
  • Updated tracer benchmark and tests to align with the new logger lifecycle and the raw JSON structLogs representation.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
eth/tracers/logger/logger.go Implements streaming vs buffered struct logging; changes structLogs buffering format and limit semantics.
cmd/evm/runner.go Switches CLI debug tracing to streaming output; adds local helper for printing EVM logs.
eth/tracers/tracers_test.go Updates tracer benchmark to new hook lifecycle / tracer attachment approach.
eth/tracers/api_test.go Updates expected ExecutionResult.StructLogs type to []json.RawMessage.
core/vm/runtime/runtime_test.go Reworks opcode-cost assertion test to use a minimal OnOpcode hook instead of StructLogs().

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

…aming ethereum#30806 ethereum#33227

Refactor StructLogger so it can either buffer legacy trace results for
RPC responses or stream formatted output directly to the CLI.

Switch cmd/evm debug tracing to the streaming path and keep debug.traceCall
on the buffered path so it can still return structured trace results.

Update the tracer benchmark and related tests to match the new hook-based
logger lifecycle and the raw JSON structLogs representation.

Treat the struct logger limit as a response-size bound in bytes instead of
counting collected trace entries.
@gzliudan gzliudan changed the title refactor(cmd/evm,eth/tracers): stream struct logger output #30806 refactor(cmd/evm,eth/tracers): refactor structlogger and make it streaming #30806 #33227 Apr 8, 2026
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.

3 participants