fix: forward transaction non-blocking context canceled

[yiweichi]

1. Purpose or design rationale of this PR

This PR fixes the issue "context canceled" when forwarding transaction to sequencer non-blocking.

2. PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation-only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

3. Deployment tag versioning

Has the version in params/version.go been updated?

• This PR doesn't involve a new deployment, git tag, docker image tag, and it doesn't affect traces
• Yes

4. Breaking change label

Does this PR have the breaking-change label?

• This PR is not a breaking change
• Yes

Summary by CodeRabbit

• Bug Fixes
  • Improved reliability of asynchronous transaction forwarding by adding a timeout and clearer debug messages on failure.
  • Updated configuration to better control transaction broadcast behavior.

[coderabbitai]

Walkthrough

The asynchronous transaction forwarding logic in the SendTx method of EthAPIBackend was updated to use a new context with a 5-second timeout for calls to sendToSequencer within a goroutine. The warning log message was also revised to clarify that failures occurred during asynchronous forwarding. Additionally, the initialization of the APIBackend field in the Ethereum struct was changed to use the GossipTxBroadcastDisabled configuration flag instead of GossipTxReceivingDisabled. The patch version constant was incremented from 1 to 2.

Changes

Cohort / File(s)	Change Summary
Async Forwarding Context and Logging eth/api_backend.go	Updated async transaction forwarding to use a 5-second timeout context for sendToSequencer calls; improved warning log message for async forwarding failures (changed to debug level).
Configuration Flag Adjustment eth/backend.go	Changed initialization of EthAPIBackend in Ethereum.New to use config.GossipTxBroadcastDisabled instead of config.GossipTxReceivingDisabled.
Version Increment params/version.go	Incremented patch version constant VersionPatch from 1 to 2.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

• refactor: make tx forwarding to sequencer non-blocking if tx pool is enabled #1227: Further refines asynchronous transaction forwarding in SendTx by introducing a background context with timeout for calls to sendToSequencer.
• feat: forward txs to sequencer #1208: Introduces initial asynchronous transaction forwarding logic, configuration flags, and RPC client setup in EthAPIBackend.SendTx.

Suggested reviewers

• yiweichi
• Thegaram
• colinlyguo

Poem

A rabbit hops through code so neat,
With timeouts set and logs replete.
Five seconds wait, then off it goes,
Async paths where context flows.
Bugs beware, this bunny’s keen—
Forwarding safe, robust, and clean! 🐇✨

---

📜 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 6e42585 and e1b3fc9.

📒 Files selected for processing (1)

• params/version.go (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• params/version.go

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (go)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-forward-tx-context-canceled

---

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

Support

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

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 generate unit tests to generate unit tests for 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.