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 update deps workflow: buf is not found #2737

Merged
merged 3 commits into from
Nov 13, 2024

Conversation

vankichi
Copy link
Contributor

@vankichi vankichi commented Nov 11, 2024

Description

SSIA

Related Issue

Versions

  • Vald Version: v1.7.13
  • Go Version: v1.23.2
  • Rust Version: v1.81.0
  • Docker Version: v27.3.1
  • Kubernetes Version: v1.31.1
  • Helm Version: v3.16.2
  • NGT Version: v2.2.4
  • Faiss Version: v1.9.0

Checklist

Special notes for your reviewer

Summary by CodeRabbit

  • Chores
    • Updated the dependency management workflow to include an additional step for handling dependency updates.

Copy link
Contributor

coderabbitai bot commented Nov 11, 2024

📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request modifies the workflow file .github/workflows/update-deps.yaml by adding the command make deps to the update-version job. This addition occurs after the make update command and is intended to facilitate dependency updates as part of the overall update process. The remaining steps of the workflow, including checking differences, labeling, and creating a pull request, remain unchanged.

Changes

File Path Change Summary
.github/workflows/update-deps.yaml Added make deps command to the update-version job after make update.

Possibly related PRs

Suggested labels

type/ci, size/S, actions/backport/release/v1.7

Suggested reviewers

  • datelier
  • kmrmt

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.

@vdaas-ci
Copy link
Collaborator

[CHATOPS:HELP] ChatOps commands.

  • 🙆‍♀️ /approve - approve
  • 🍱 /format - format codes and add licenses
  • /gen-test - generate test codes
  • 🏷️ /label - add labels
  • 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

Copy link
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

🧹 Outside diff range and nitpick comments (2)
.github/workflows/update-deps.yaml (2)

Line range hint 71-77: Fix the version comparison syntax in the shell script.

The current version comparison has incorrect syntax which could lead to unexpected behavior:

  • ${LATEST} eq "1.7" is invalid bash syntax
  • eq is not a valid bash comparison operator

Apply this fix:

-          if ${LATEST} eq "1.7"; then
+          if [ "${LATEST}" = "1.7" ]; then

Line range hint 44-54: Consider adding error handling for the dependency update commands.

The sequence of make commands could fail silently. Consider adding error checking to ensure each step completes successfully.

Example improvement:

       run: |
+         set -e  # Exit on any error
          make files
          make update
          make deps
          make helm/schema/all
          # ... rest of commands ...
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a583f09 and bb5f13e.

📒 Files selected for processing (1)
  • .github/workflows/update-deps.yaml (1 hunks)
🔇 Additional comments (1)
.github/workflows/update-deps.yaml (1)

45-45: LGTM! Verify the make deps target exists.

The addition of make deps should help resolve the missing 'buf' tool issue.

Let's verify the existence and implementation of the deps target:

✅ Verification successful

The make deps target exists and is properly implemented

The deps target is defined in the Makefile with the following dependencies:

  • proto/deps
  • deps/install

The deps/install target is also defined and installs various development tools:

  • crlfmt
  • golines
  • gofumpt
  • strictgoimports
  • goimports

This implementation appears correct and complete for handling dependencies.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the make deps target exists and its implementation
# Expected: Find the deps target definition that handles buf installation

# Search for deps target in Makefile
rg -A 5 '^deps:' Makefile

# Search for buf-related commands in Makefiles
rg -g 'Makefile*' 'buf'

Length of output: 301


Script:

#!/bin/bash
# Let's check the implementation of buf/install target and deps/install target
rg -A 5 '^buf/install:' Makefile
rg -A 5 '^deps/install:' Makefile

# Also check the proto/deps target as it's part of the deps dependency chain
rg -A 5 '^proto/deps:' Makefile

Length of output: 224


Script:

#!/bin/bash
# Let's check for buf-related targets with different patterns and more context
rg -g 'Makefile*' -B 2 -A 5 'buf' --context-separator='---'

# Also check if there are any other Makefiles in subdirectories
fd Makefile

Length of output: 730


Script:

#!/bin/bash
# Let's check the content of the other Makefiles and the Makefile.d directory
cat internal/core/algorithm/ngt/Makefile
ls -la Makefile.d/
cat Makefile.d/*

Length of output: 129207

Copy link

cloudflare-workers-and-pages bot commented Nov 11, 2024

Deploying vald with  Cloudflare Pages  Cloudflare Pages

Latest commit: cefb26a
Status: ✅  Deploy successful!
Preview URL: https://bf3e91ee.vald.pages.dev
Branch Preview URL: https://ci-workflow-fix-ci-error-buf.vald.pages.dev

View logs

@kpango kpango merged commit 9c52696 into main Nov 13, 2024
50 checks passed
@kpango kpango deleted the ci/workflow/fix-ci-error-buf-command-not-found branch November 13, 2024 04:55
vdaas-ci pushed a commit that referenced this pull request Nov 13, 2024
vankichi added a commit that referenced this pull request Nov 13, 2024
kpango pushed a commit that referenced this pull request Nov 14, 2024
kpango added a commit that referenced this pull request Nov 14, 2024
kpango added a commit that referenced this pull request Nov 14, 2024
kpango added a commit that referenced this pull request Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants