Skip to content

chore(ci): build docker with metrics#6916

Merged
SWvheerden merged 2 commits intotari-project:developmentfrom
ns212:ci-docker
Apr 4, 2025
Merged

chore(ci): build docker with metrics#6916
SWvheerden merged 2 commits intotari-project:developmentfrom
ns212:ci-docker

Conversation

@ns212
Copy link
Copy Markdown
Contributor

@ns212 ns212 commented Apr 3, 2025

Description

Build minotari_node with metrics feature enabled; Remove unused feature flags;

Motivation and Context

How Has This Been Tested?

Tested on a seed node.

What process can a PR reviewer use to test or verify this change?

Breaking Changes

  • None
  • Requires data directory on base node to be deleted
  • Requires hard fork
  • Other - Please specify

Summary by CodeRabbit

  • New Features
    • Updated the default container configuration to include an expanded set of capabilities for enhanced performance and monitoring.
    • Improved container startup reliability with a new process management component that ensures smoother signal handling and process reaping.

@ns212 ns212 requested a review from a team as a code owner April 3, 2025 04:58
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 3, 2025

Walkthrough

The changes update two configuration files. In the GitHub Actions workflow YAML, the default value of the features input parameter is changed from "safe,grpc" to "safe,libtor,metrics". In the Dockerfile under buildtools/docker_rig/, the tini package has been added to the installation command. There are no alterations to the control flow or other structural changes in either configuration.

Changes

File Change Summary
.github/workflows/build_dockers_workflow.yml Updated the default value of the features input parameter from "safe,grpc" to "safe,libtor,metrics"
buildtools/.../tarilabs.Dockerfile Added the installation of the tini package to the apt-get install command

Poem

Hop along with glee, a rabbit's cheer in sight,
For tiny tweaks in code that now shine bright.
Features hop from old to new, leaping with delight,
And tiny tini joins the crew—oh, what a sight!
Bugs flee and processes flow, coding feels just right.
🐇💻 Enjoy these changes, day and night!
(Bounce, bounce, the code’s in flight!)


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
🪧 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 plan to trigger planning for file edits and PR creation.
  • @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.

Copy link
Copy Markdown
Contributor

@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 (2)
buildtools/docker_rig/tarilabs.Dockerfile (1)

124-125: Verify the addition of the tini package.
The addition of tini in the list of packages is a good move for handling process reaping and signal forwarding in the container. Please ensure that the default version shipped with the OS base (Bookworm) meets your requirements. If version consistency is a concern, consider pinning the package version.

.github/workflows/build_dockers_workflow.yml (1)

21-24: Confirm the updated default value for the features input parameter.
The default value has been updated from 'safe,grpc' to 'safe,libtor,metrics', reflecting the removal of unused feature flags and the addition of metrics support. Please verify that this change is aligned with the overall feature set and that any documentation or dependent configurations have been updated accordingly.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between df406c6 and b890b60.

📒 Files selected for processing (2)
  • .github/workflows/build_dockers_workflow.yml (1 hunks)
  • buildtools/docker_rig/tarilabs.Dockerfile (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: test (mainnet, stagenet)
  • GitHub Check: test (nextnet, nextnet)
  • GitHub Check: test (testnet, esmeralda)
  • GitHub Check: ci
  • GitHub Check: cargo check with stable
  • GitHub Check: Cucumber tests / Base Layer
  • GitHub Check: Cucumber tests / FFI

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 3, 2025

Test Results (CI)

    3 files    129 suites   44m 52s ⏱️
1 353 tests 1 353 ✅ 0 💤 0 ❌
4 057 runs  4 057 ✅ 0 💤 0 ❌

Results for commit 917bd05.

♻️ This comment has been updated with latest results.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 3, 2025

Test Results (Integration tests)

36 tests  +36   36 ✅ +36   16m 27s ⏱️ + 16m 27s
11 suites +11    0 💤 ± 0 
 2 files   + 2    0 ❌ ± 0 

Results for commit 917bd05. ± Comparison against base commit cef46a5.

♻️ This comment has been updated with latest results.

features:
type: string
default: 'safe,grpc'
default: 'safe,libtor,metrics'
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we not keep grpc?
libtor is the default for nix, but having it in seems more clear.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think we do need grpc for the block explorers

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I removed it because I don't see grpc defined as a feature flag anymore

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

what are we building here?
I see the base node only has has grpc as a config option not compile feature

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Docker images for tari_suite.

Console wallet has the empty feature too. Was it not meant as a none default build feature?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I did local build with and without grpc feature, and my base node still started up, so I think this can go in.

@SWvheerden SWvheerden changed the title feat(ci): build docker with metrics chore(ci): build docker with metrics Apr 3, 2025
@SWvheerden SWvheerden merged commit 1084304 into tari-project:development Apr 4, 2025
17 checks passed
sdbondi added a commit to sdbondi/tari that referenced this pull request Apr 7, 2025
* development:
  fix(p2p/dns): greatly simplify DNS TXT lookup (tari-project#6922)
  feat: handle outbound pipeline interlock due to connection cleanup (tari-project#6921)
  chore(ci): build docker with metrics (tari-project#6916)
sdbondi added a commit to sdbondi/tari that referenced this pull request Apr 8, 2025
* development:
  fix(p2p/dns): greatly simplify DNS TXT lookup (tari-project#6922)
  feat: handle outbound pipeline interlock due to connection cleanup (tari-project#6921)
  chore(ci): build docker with metrics (tari-project#6916)
sdbondi added a commit to sdbondi/tari that referenced this pull request Apr 8, 2025
* development:
  fix(p2p/dns): greatly simplify DNS TXT lookup (tari-project#6922)
  feat: handle outbound pipeline interlock due to connection cleanup (tari-project#6921)
  chore(ci): build docker with metrics (tari-project#6916)
sdbondi added a commit to sdbondi/tari that referenced this pull request Apr 8, 2025
* development:
  fix(p2p/dns): greatly simplify DNS TXT lookup (tari-project#6922)
  feat: handle outbound pipeline interlock due to connection cleanup (tari-project#6921)
  chore(ci): build docker with metrics (tari-project#6916)
sdbondi added a commit to sdbondi/tari that referenced this pull request Apr 9, 2025
* development:
  fix(p2p/dns): greatly simplify DNS TXT lookup (tari-project#6922)
  feat: handle outbound pipeline interlock due to connection cleanup (tari-project#6921)
  chore(ci): build docker with metrics (tari-project#6916)
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