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: slow log to info #2935

Open
wants to merge 1 commit into
base: unstable
Choose a base branch
from

Conversation

Mixficsol
Copy link
Collaborator

@Mixficsol Mixficsol commented Oct 28, 2024

将慢日志级别调整为 INFO

Summary by CodeRabbit

  • New Features
    • Introduced a new job for building a Docker image for Pika.
  • Improvements
    • Updated the macOS build environment to version 13.
    • Enhanced the Rocky Linux build process with new package installations and environment configurations.
  • Bug Fixes
    • Adjusted logging level from error to informational for slow command detection.

Copy link

coderabbitai bot commented Oct 28, 2024

Walkthrough

The pull request introduces several changes to the GitHub Actions workflow located in .github/workflows/pika.yml. Key updates include modifying the build_on_macos job to run on macos-13, updating the build_on_rocky job to utilize dnf for package management and adding gcc-toolset-13. A new job, build_pika_image, is introduced for building a Docker image, which depends on the successful completion of the build_on_ubuntu job. Additionally, a logging level change is made in the ProcessSlowlog method of the PikaClientConn class.

Changes

File Change Summary
.github/workflows/pika.yml - Updated build_on_macos to run on macos-13.
- Modified build_on_rocky for dnf usage and added gcc-toolset-13.
- Added build_pika_image job for Docker image creation.
src/pika_client_conn.cc - Changed logging in ProcessSlowlog from LOG(ERROR) to LOG(INFO).

Possibly related PRs

  • fix:fix CI #2924: The changes in this PR also involve modifications to the .github/workflows/pika.yml file, including updates to the build_on_macos, build_on_rocky, and the addition of the build_pika_image job, which directly relate to the changes made in the main PR.

Suggested labels

☢️ Bug

Poem

In the land of code, where rabbits play,
We hop and build, come what may.
With Docker images and macOS bright,
Our workflow's ready, oh what a sight!
From slow logs to packages anew,
Hopping along, we code just for you! 🐇✨


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

@github-actions github-actions bot added the ☢️ Bug Something isn't working label Oct 28, 2024
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

🧹 Outside diff range and nitpick comments (1)
.github/workflows/pika.yml (1)

Line range hint 1-248: Consider splitting unrelated changes.

The workflow file changes (MacOS version upgrade, Rocky Linux package management, and Docker image addition) appear to be independent of the logging level changes mentioned in the PR title. Consider splitting these into separate PRs for better traceability and easier review.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b5cdb2f and c5cbb1f.

📒 Files selected for processing (2)
  • .github/workflows/pika.yml (2 hunks)
  • src/pika_client_conn.cc (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • src/pika_client_conn.cc
🔇 Additional comments (3)
.github/workflows/pika.yml (3)

159-159: LGTM: MacOS runner and cache key updates are consistent.

The changes to update both the MacOS runner version and its corresponding cache key from macos-12 to macos-13 are properly aligned.

Also applies to: 172-172


Line range hint 1-248: Verify Docker build context.

The new Docker image build job references ./ci/Dockerfile, but we should verify its existence and contents to ensure proper build context.

#!/bin/bash
# Check if Dockerfile exists and examine its contents
if [ -f "./ci/Dockerfile" ]; then
    echo "Dockerfile found. Contents:"
    cat "./ci/Dockerfile"
else
    echo "Dockerfile not found at ./ci/Dockerfile"
fi

# Check if the artifact path matches Dockerfile expectations
rg -l "artifact/" ci/

Line range hint 159-248: Verify MacOS dependencies compatibility.

While the MacOS version upgrade is straightforward, it's important to ensure all installed dependencies are compatible with macos-13.

✅ Verification successful

Let me gather more information about the MacOS dependencies by checking the build history and any related discussions.


Let me check one more aspect - the recent workflow runs to see if there are any build issues with these dependencies on macos-13.


Dependencies are compatible with macos-13

The verification shows that:

  • The project already has successful builds on macos-13 as evidenced by the existing workflow configuration
  • The specified dependencies (gcc@10, [email protected], protobuf, llvm) are standard packages available through Homebrew
  • The compiler configuration is properly set up with gcc-10 which is known to work on macos-13
  • No specific version constraints or compatibility issues are documented
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any macos-specific version constraints or known issues in docs
rg -i "macos.*1[23]" README.md docs/

Length of output: 610


Script:

#!/bin/bash
# Check build history and discussions for macos-13 related issues
rg -i "macos.*(1[23]|monterey|ventura)" .github/
# Check if there are any specific version constraints for the installed packages
rg -i "brew.*(python@3\.12|gcc@10|protobuf|llvm)" .github/
# Look for any build failure logs or discussions related to these dependencies
rg -i "(fail|error|issue).*brew.*(install|upgrade)" .github/

Length of output: 521


Script:

#!/bin/bash
# Check if there are any recent changes or discussions about these specific package versions
rg -i "version.*(python|gcc|protobuf|llvm)" .github/
# Look for any specific macos configuration or setup in the codebase
rg -i "macos.*setup|configuration" .github/
# Check for any compiler-specific settings or requirements
rg -i "(CC|CXX|COMPILER).*(gcc|clang)" .github/

Length of output: 1715

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
☢️ Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant