feat(gas-oracle): add a warn log when entering fallback mode

[colinlyguo]

Purpose or design rationale of this PR

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:

• feat: A new feature

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• Yes

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change

Summary by CodeRabbit

• Bug Fixes
  • Improved logging to warn users when batch processing is delayed due to high gas fees, providing more visibility into fee adjustments.
• Chores
  • Updated version number to v4.5.5.

[coderabbitai]

"""

Walkthrough

This update increments the version tag from "v4.5.4" to "v4.5.5" in the versioning file. Additionally, it introduces a new warning log statement in the ProcessGasPriceOracle method within the Layer1Relayer struct. The log notifies when a batch has been stuck for an extended period, likely due to increased L1 gas fees, and records the current base fee and blob base fee before these values are reset to their defaults. No other logic or control flow changes are present.

Changes

File(s)	Change Summary
common/version/version.go	Updated the version tag string from "v4.5.4" to "v4.5.5".
rollup/internal/controller/relayer/l1_relayer.go	Added a warning log in ProcessGasPriceOracle to indicate when batch is stuck and fees reset.

Possibly related PRs

• fix(gas-oracle): check blob gas fee before entering default gas price mode #1565: Modifies the same ProcessGasPriceOracle method and Layer1Relayer struct, focusing on gas price handling and conditions for entering default gas price mode.

Suggested labels

bump-version

Suggested reviewers

• georgehao

Poem

A version hop, from four-five-four
To four-five-five, we soar!
A warning log now hops in place,
To catch the fees that run a race.
When batches stall and fees run high,
The relayer gives a rabbit sigh—
And logs before it resets, oh my! 🐇
"""

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 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 6a41624 and 230d10b.

📒 Files selected for processing (1)

• rollup/internal/controller/relayer/l1_relayer.go (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• rollup/internal/controller/relayer/l1_relayer.go

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

• GitHub Check: tests

---

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

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 41.22%. Comparing base (a77f141) to head (230d10b).

Files with missing lines	Patch %	Lines
rollup/internal/controller/relayer/l1_relayer.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1646      +/-   ##
===========================================
- Coverage    41.23%   41.22%   -0.01%     
===========================================
  Files          222      222              
  Lines        18166    18167       +1     
===========================================
  Hits          7490     7490              
- Misses        9947     9948       +1     
  Partials       729      729              

Flag	Coverage Δ
rollup	51.86% <0.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.