Skip to content
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

fix(build): image building #1603

Merged
merged 6 commits into from
Feb 26, 2025
Merged

fix(build): image building #1603

merged 6 commits into from
Feb 26, 2025

Conversation

colinlyguo
Copy link
Member

@colinlyguo colinlyguo commented Feb 26, 2025

Purpose or design rationale of this PR

This PR fixes go.work.sync update in image building and fixes compile errors in rollup-relayer and gas-oracle. It also changes the base images of rollup-db-cli and bridgehistoryapi-db-cli to Ubuntu, making them compatible with .a files in da-codec's zstd library.

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:

  • fix: A bug fix

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

  • Chores

    • Updated the application version to v4.4.89.
    • Improved build and deployment setups by switching to updated container images and adding necessary build flags.
  • Refactor

    • Consolidated fee calculation dependencies to streamline internal logic without altering functionality.

Copy link

coderabbitai bot commented Feb 26, 2025

Warning

Rate limit exceeded

@colinlyguo has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 21 minutes and 19 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 0918cdd and ec9f65f.

📒 Files selected for processing (2)
  • build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (2 hunks)
  • build/dockerfiles/db_cli.Dockerfile (2 hunks)

Walkthrough

The pull request updates the version tag in common/version/version.go from "v4.4.88" to "v4.4.89". Additionally, it modifies several Dockerfiles to change base images and build commands, reflecting adjustments in the build and deployment environments. The import paths and function calls in two Go files have also been updated to source a function from a different package, while preserving the overall functionality.

Changes

File Change Summary
common/.../version.go Updated version tag from "v4.4.88" to "v4.4.89".
build/dockerfiles/.../db_cli.Dockerfile Updated base image to scrolltech/go-rust-builder:go-1.21-rust-nightly-2023-12-03, changed deployment base image to ubuntu:20.04, added ENV CGO_LDFLAGS="-ldl".
build/dockerfiles/.../bridgehistoryapi-db-cli.Dockerfile Updated base image to scrolltech/go-rust-builder:go-1.21-rust-nightly-2023-12-03, changed deployment base image to ubuntu:20.04, added ENV CGO_LDFLAGS="-ldl".
rollup/internal/controller/.../sender.go Updated import path for CalcBlobFee from eip4844 to misc, modified the corresponding function call.
rollup/internal/controller/.../l1_watcher.go Updated import path for CalcBlobFee from eip4844 to misc, modified the corresponding function call.

Possibly related PRs

Suggested reviewers

  • georgehao
  • Thegaram

Poem

I'm a rabbit in the code field, so spry,
Hopping to a new version, reaching the sky.
v4.4.89 bounds in with a joyful beat,
A tiny change making our code complete.
With soft paw-prints and a happy chime,
CodeRabbit sings versioned tales in rhyme!


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?

❤️ Share
🪧 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
Copy link

codecov-commenter commented Feb 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.72%. Comparing base (5b6b145) to head (ec9f65f).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1603   +/-   ##
========================================
  Coverage    51.72%   51.72%           
========================================
  Files          157      157           
  Lines        12555    12555           
========================================
  Hits          6494     6494           
  Misses        5497     5497           
  Partials       564      564           
Flag Coverage Δ
rollup 56.99% <100.00%> (ø)

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.

Copy link

@coderabbitai coderabbitai bot left a 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

🧹 Nitpick comments (1)
build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (1)

16-16: Changed Final Stage Base Image to Ubuntu.
The deployment stage now uses ubuntu:20.04 in place of the previous alpine image. This change may offer improved compatibility with system dependencies; however, it can also lead to a larger image size. Consider reviewing whether a slimmer variant (e.g., ubuntu:20.04-slim) might better suit your runtime constraints.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f42d7e8 and 68b29e7.

📒 Files selected for processing (1)
  • build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (17)
  • GitHub Check: rollup-db-cli
  • GitHub Check: rollup_relayer
  • GitHub Check: gas_oracle
  • GitHub Check: coordinator-cron
  • GitHub Check: bridgehistoryapi-db-cli
  • GitHub Check: bridgehistoryapi-api
  • GitHub Check: coordinator-api
  • GitHub Check: bridgehistoryapi-fetcher
  • GitHub Check: tests
  • GitHub Check: tests
  • GitHub Check: tests
  • GitHub Check: tests
  • GitHub Check: check
  • GitHub Check: check
  • GitHub Check: check
  • GitHub Check: tests
  • GitHub Check: check
🔇 Additional comments (2)
build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (2)

2-2: Updated Base Image for Build Dependencies.
The base image is now scrolltech/go-rust-builder:go-1.21-rust-nightly-2023-12-03, which integrates both Go 1.21 and Rust nightly tooling. Please verify that this image meets all build-time requirements and is fully compatible with existing dependency installations.


17-17: Configured CGO_LDFLAGS for Linker Behavior.
The addition of the environment variable CGO_LDFLAGS="-Wl,--no-as-needed -ldl" explicitly customizes the linker behavior for Cgo, which can be crucial for managing shared libraries. Please verify that these flags are necessary for your use-case and do not introduce unintended side effects during linking.

Copy link

@coderabbitai coderabbitai bot left a 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

🧹 Nitpick comments (1)
build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (1)

16-17: Revisit Runtime Base Image and Environment Variable Usage.
The runtime stage now uses ubuntu:20.04 instead of Alpine. While Ubuntu may offer a richer library ecosystem, note the potential trade-off with a larger image size. Additionally, the environment variable CGO_LDFLAGS is set again in this stage—ensure that this setting is intended for the runtime environment (typically, these flags are most relevant during compilation) and that the Ubuntu image includes all necessary runtime dependencies.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 68b29e7 and 6f6b50e.

📒 Files selected for processing (1)
  • build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (17)
  • GitHub Check: rollup-db-cli
  • GitHub Check: rollup_relayer
  • GitHub Check: gas_oracle
  • GitHub Check: coordinator-cron
  • GitHub Check: bridgehistoryapi-api
  • GitHub Check: coordinator-api
  • GitHub Check: bridgehistoryapi-fetcher
  • GitHub Check: bridgehistoryapi-db-cli
  • GitHub Check: tests
  • GitHub Check: tests
  • GitHub Check: tests
  • GitHub Check: check
  • GitHub Check: tests
  • GitHub Check: check
  • GitHub Check: check
  • GitHub Check: check
  • GitHub Check: tests
🔇 Additional comments (2)
build/dockerfiles/bridgehistoryapi-db-cli.Dockerfile (2)

2-2: Updated Base Image to Include Go and Rust Tooling.
The base image has been changed to scrolltech/go-rust-builder:go-1.21-rust-nightly-2023-12-03, which integrates both Go and Rust toolchains. Please verify that this image meets your security, compatibility, and maintenance standards, given its role in the new build environment.


11-13: Validate the Build Command and Linker Flags.
The build command now employs a multi-mount approach and explicitly sets CGO_LDFLAGS to "-Wl,--no-as-needed -ldl" when building db_cli. Double-check that these linker flags are necessary for your project requirements and that the directory /src/bridge-history-api/cmd/db_cli is correctly structured in the build context.

@colinlyguo colinlyguo added the bump-version Bump the version tag for deployment label Feb 26, 2025
@colinlyguo colinlyguo changed the title fix(build): fix go.work.sum fix(build): update dependencies and change base image of rollup-db-cli and bridgehistoryapi-db-cli Feb 26, 2025
georgehao
georgehao previously approved these changes Feb 26, 2025
Thegaram
Thegaram previously approved these changes Feb 26, 2025
@colinlyguo colinlyguo changed the title fix(build): update dependencies and change base image of rollup-db-cli and bridgehistoryapi-db-cli fix(build): image building Feb 26, 2025
@colinlyguo colinlyguo merged commit 6b837c0 into develop Feb 26, 2025
14 checks passed
@colinlyguo colinlyguo deleted the fix-go-work-sum branch February 26, 2025 13:14
@coderabbitai coderabbitai bot mentioned this pull request Feb 26, 2025
3 tasks
@coderabbitai coderabbitai bot mentioned this pull request Mar 10, 2025
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump-version Bump the version tag for deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants