fix: remove redundant event emission in ApplyTransaction method

[dreamer-zq]

fix: #2997

Summary by CodeRabbit

• Refactor
  • Updated event handling during post-transaction processing to streamline event management. No changes to user-facing functionality.

[coderabbitai]

Walkthrough

The change removes the explicit emission of events from the temporary context's event manager to the main context's event manager after committing the temporary context in the EVM state transition logic. All other transaction post-processing logic remains unchanged.

Changes

File(s)	Change Summary
modules/evm/state_transition.go	Removed explicit event emission from temporary to main context after commit.

Sequence Diagram(s)

sequenceDiagram
    participant MainCtx as Main Context
    participant TmpCtx as Temporary Context
    participant Commit as Commit Function

    MainCtx->>TmpCtx: Create CacheContext
    TmpCtx->>TmpCtx: PostTxProcessing
    alt PostTxProcessing successful
        TmpCtx->>Commit: Commit()
        Commit->>MainCtx: Internal event emission (handled by SDK)
        Commit->>TmpCtx: Write changes
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Remove duplicate event emission after committing CacheContext (#2997)	✅
Ensure only single event emission occurs post-transaction processing (#2997)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Poem

A hop, a skip, a single cheer,
No double echoes for us to hear!
Events now march just once in line,
The code is clean, the logs are fine.
With every hop, this bunny grins—
For duplicate events, the fix now wins!
🐇✨

---

📜 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 1f2335f and 534265a.

📒 Files selected for processing (1)

• modules/evm/state_transition.go (0 hunks)

💤 Files with no reviewable changes (1)

• modules/evm/state_transition.go

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

• GitHub Check: Run Unit Tests
• GitHub Check: Analyze (go)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

• 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.