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 go build argument #2806

Merged
merged 2 commits into from
Jan 22, 2025
Merged

Conversation

kmrmt
Copy link
Contributor

@kmrmt kmrmt commented Jan 22, 2025

Description

SSIA

Related Issue

Versions

  • Vald Version: v1.7.15
  • Go Version: v1.23.4
  • Rust Version: v1.83.0
  • Docker Version: v27.4.0
  • Kubernetes Version: v1.32.0
  • Helm Version: v3.16.3
  • NGT Version: v2.3.5
  • Faiss Version: v1.9.0

Checklist

Special notes for your reviewer

Summary by CodeRabbit

  • Build Process
    • Updated build configuration across multiple Dockerfiles to include both organization and repository names in the build command.
    • Standardized repository path specification during application compilation.
  • Dependency Updates
    • Incremented Go version from 1.23.4 to 1.23.5.
    • Updated various dependencies across multiple modules for compatibility and improvements.

Copy link
Contributor

coderabbitai bot commented Jan 22, 2025

📝 Walkthrough

Walkthrough

This pull request involves modifications to multiple Dockerfiles across various components of the project. The primary change is consistent across all files: updating the REPO argument in the make command from REPO="${ORG}" to REPO="${ORG}/${REPO}". This modification changes how the repository is referenced during the build process, potentially altering the context of repository path construction. The changes affect Dockerfiles in different directories, including agent, discoverer, gateway, index, manager, and tools components.

Changes

Path Change Summary
dockers/*/Dockerfile Updated make command to use REPO="${ORG}/${REPO}" instead of REPO="${ORG}"
Specific files include: - agent/core/faiss/Dockerfile
- agent/core/ngt/Dockerfile
- agent/sidecar/Dockerfile
- discoverer/k8s/Dockerfile
- example/client/Dockerfile
- gateway/filter/Dockerfile
- gateway/lb/Dockerfile
- gateway/mirror/Dockerfile
- index/job/correction/Dockerfile
- index/job/creation/Dockerfile
- index/job/deletion/Dockerfile
- index/job/readreplica/rotate/Dockerfile
- index/job/save/Dockerfile
- index/operator/Dockerfile
- manager/index/Dockerfile
- tools/benchmark/job/Dockerfile
- tools/benchmark/operator/Dockerfile
- tools/cli/loadtest/Dockerfile

Possibly related PRs

  • add check context cancel #2596: The changes in this PR involve modifications to the Dockerfile that affect the REPO argument in the make command, similar to the changes made in the main PR regarding the REPO argument in the Dockerfile.
  • feat: add usearch #2608: This PR also modifies a Dockerfile to change the REPO argument in the make command, aligning with the changes made in the main PR.
  • Bugfix vald-helm-operator build error #2610: The changes in this PR include updates to the REPO argument in the make command within a Dockerfile, which is directly related to the changes in the main PR.

Suggested Labels

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

Suggested Reviewers

  • hlts2
  • vankichi

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. (Beta)
  • @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

@github-actions github-actions bot added size/M type/bug Something isn't working priority/medium labels Jan 22, 2025
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

🧹 Nitpick comments (2)
dockers/tools/benchmark/job/Dockerfile (1)

88-88: LGTM! Change completes the fix.

The change to the REPO argument is consistent with all other Dockerfiles, completing the necessary modifications to fix the Go build arguments.

This systematic change across all Dockerfiles improves the build process by:

  1. Using a more explicit repository path structure
  2. Maintaining consistency across all components
  3. Properly handling the organization/repository hierarchy
dockers/agent/core/faiss/Dockerfile (1)

90-90: LGTM! Fix consistently applied across Dockerfiles.

The repository path fix is correctly implemented here as well. This change, along with the similar changes in other Dockerfiles, ensures that the Go build process uses the correct repository path format throughout the project.

This fix ensures proper Go module path resolution during builds, which is crucial for:

  1. Correct package imports
  2. Proper versioning
  3. Consistent module resolution across different build environments
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8179e7d and 0487619.

⛔ Files ignored due to path filters (1)
  • hack/docker/gen/main.go is excluded by !**/gen/**
📒 Files selected for processing (18)
  • dockers/agent/core/faiss/Dockerfile (1 hunks)
  • dockers/agent/core/ngt/Dockerfile (1 hunks)
  • dockers/agent/sidecar/Dockerfile (1 hunks)
  • dockers/discoverer/k8s/Dockerfile (1 hunks)
  • dockers/example/client/Dockerfile (1 hunks)
  • dockers/gateway/filter/Dockerfile (1 hunks)
  • dockers/gateway/lb/Dockerfile (1 hunks)
  • dockers/gateway/mirror/Dockerfile (1 hunks)
  • dockers/index/job/correction/Dockerfile (1 hunks)
  • dockers/index/job/creation/Dockerfile (1 hunks)
  • dockers/index/job/deletion/Dockerfile (1 hunks)
  • dockers/index/job/readreplica/rotate/Dockerfile (1 hunks)
  • dockers/index/job/save/Dockerfile (1 hunks)
  • dockers/index/operator/Dockerfile (1 hunks)
  • dockers/manager/index/Dockerfile (1 hunks)
  • dockers/tools/benchmark/job/Dockerfile (1 hunks)
  • dockers/tools/benchmark/operator/Dockerfile (1 hunks)
  • dockers/tools/cli/loadtest/Dockerfile (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (180)
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
🔇 Additional comments (16)
dockers/agent/sidecar/Dockerfile (1)

80-80: Verify the repository path fix in the Makefile.

The change from REPO="${ORG}" to REPO="${ORG}/${REPO}" appears to fix an issue with the Go build argument. Let's verify how this value is used in the Makefile.

✅ Verification successful

The repository path change in the Dockerfile is correct

The change from REPO="${ORG}" to REPO="${ORG}/${REPO}" aligns with the Makefile's definition REPO = $(ORG)/$(NAME) and is used correctly for Go package paths and workspace directories.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check how REPO argument is used in the Makefile and related build files

# Check Makefile for REPO usage
echo "=== Checking Makefile for REPO usage ==="
rg -A 3 'REPO.*:=|REPO.*=|REPO.*\?=' Makefile

# Check for any Go-related build targets that use REPO
echo "=== Checking Go-related build targets ==="
rg -A 5 'go\s+build|go\s+install' Makefile

# Check the template that generates these Dockerfiles
echo "=== Checking Dockerfile generator ==="
rg -A 3 'REPO' hack/docker/gen/main.go

Length of output: 1667

dockers/gateway/lb/Dockerfile (1)

80-80: Consistent fix applied across Dockerfiles.

The repository path construction has been fixed consistently across all Dockerfiles. This change ensures the correct repository path is used during the build process.

dockers/manager/index/Dockerfile (1)

80-80: Consistent fix applied across Dockerfiles.

The repository path construction has been fixed consistently across all Dockerfiles. This change ensures the correct repository path is used during the build process.

dockers/gateway/mirror/Dockerfile (1)

80-80: Consistent fix applied across Dockerfiles.

The repository path construction has been fixed consistently across all Dockerfiles. This change ensures the correct repository path is used during the build process.

dockers/gateway/filter/Dockerfile (1)

80-80: Consistent fix applied across Dockerfiles.

The repository path construction has been fixed consistently across all Dockerfiles. This change ensures the correct repository path is used during the build process.

dockers/index/job/save/Dockerfile (1)

80-80: LGTM! The fix correctly sets the repository path.

The change from REPO="${ORG}" to REPO="${ORG}/${REPO}" properly constructs the full repository path as "vdaas/vald" instead of just "vdaas". This is a critical fix that ensures the correct repository context during the build process.

Since these Dockerfiles are generated, let's verify if the template needs updating:

✅ Verification successful

Template is already using the correct repository path format

The template file at hack/docker/gen/main.go already uses the correct REPO="${ORG}/${REPO}" pattern in both goBuildCommands and goExampleBuildCommands. No template updates are needed.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the template file has been updated with the fix

# Search for the make command pattern in the template
rg -A 5 'make.*REPO="\$\{ORG\}"' hack/docker/gen/main.go

# If found, it indicates the template hasn't been updated yet
if [ $? -eq 0 ]; then
    echo "Warning: Template file may need to be updated with the fix"
fi

Length of output: 76


Script:

#!/bin/bash
# Search for make commands in the template file to see the current pattern
echo "=== Searching for make commands in template ==="
rg -A 5 'make.*REPO=' hack/docker/gen/main.go

echo -e "\n=== Searching for specific ORG/REPO pattern ==="
rg 'REPO="\$\{ORG\}/\$\{REPO\}"' hack/docker/gen/main.go

Length of output: 870

dockers/discoverer/k8s/Dockerfile (1)

80-80: Same fix as in other Dockerfiles.

This change implements the same critical fix for the repository path construction.

dockers/tools/benchmark/operator/Dockerfile (1)

80-80: Same fix as in other Dockerfiles.

This change implements the same critical fix for the repository path construction.

dockers/index/operator/Dockerfile (1)

80-80: Same fix as in other Dockerfiles.

This change implements the same critical fix for the repository path construction.

dockers/index/job/deletion/Dockerfile (1)

80-80: Same fix as in other Dockerfiles.

This change implements the same critical fix for the repository path construction.

dockers/index/job/creation/Dockerfile (1)

80-80: LGTM! Verify consistency across the codebase.

The change to the REPO argument looks correct and aligns with the PR's objective to fix Go build arguments.

Let's verify that this change is consistent across all Dockerfiles:

✅ Verification successful

✅ REPO argument format is consistent across all Dockerfiles

All 18 Dockerfiles in the codebase use the same REPO="${ORG}/${REPO}" format, confirming the change is consistent.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any Dockerfiles that might still use the old REPO argument format
# Expected: No matches for the old format

echo "Checking for Dockerfiles still using the old REPO format..."
rg -g 'Dockerfile' 'make.*REPO="\$\{ORG\}".*'

echo "Verifying all Dockerfiles use the new REPO format..."
rg -g 'Dockerfile' 'make.*REPO="\$\{ORG\}/\$\{REPO\}".*'

Length of output: 3085

dockers/index/job/correction/Dockerfile (1)

80-80: LGTM!

The change to the REPO argument is consistent with other Dockerfiles.

dockers/example/client/Dockerfile (1)

88-88: LGTM!

The change to the REPO argument is consistent, properly handling the client-specific path structure.

dockers/index/job/readreplica/rotate/Dockerfile (1)

80-80: LGTM!

The change to the REPO argument maintains consistency with other Dockerfiles.

dockers/agent/core/ngt/Dockerfile (1)

89-89: LGTM! The repository path fix is correct.

The change from REPO="${ORG}" to REPO="${ORG}/${REPO}" properly constructs the full repository path as "vdaas/vald", which is the correct format for Go module paths.

Let's verify the repository structure:

✅ Verification successful

Repository structure verification successful

The change to use REPO="${ORG}/${REPO}" is verified to be correct, matching both:

  • The repository's actual structure (vdaas/vald)
  • The Go module path in go.mod (github.com/vdaas/vald)
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the repository structure matches the new REPO format

# Test 1: Check if the repository follows the ORG/REPO structure
test -d .git && echo "Repository exists" && \
git config --get remote.origin.url | grep -q "${ORG}/${REPO}" && \
echo "Repository structure matches ORG/REPO format"

# Test 2: Check if go.mod uses the correct module path
test -f go.mod && grep "^module" go.mod

Length of output: 277

dockers/tools/cli/loadtest/Dockerfile (1)

88-88: LGTM! Consistent fix applied.

The repository path fix is consistently applied here, maintaining the correct Go module path structure.

coderabbitai[bot]
coderabbitai bot previously approved these changes Jan 22, 2025
Copy link

cloudflare-workers-and-pages bot commented Jan 22, 2025

Deploying vald with  Cloudflare Pages  Cloudflare Pages

Latest commit: ce4859f
Status: ✅  Deploy successful!
Preview URL: https://3867cd34.vald.pages.dev
Branch Preview URL: https://bugfix-dockerfile-invalid-bu.vald.pages.dev

View logs

@github-actions github-actions bot added size/XXL and removed size/M labels Jan 22, 2025
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: 4

🔭 Outside diff range comments (1)
hack/go.mod.default (1)

Line range hint 6-350: Invalid dependency version specifiers in replace directives.

The use of upgrade as a version specifier is invalid in Go module files. Each dependency should specify either a valid version (e.g., v1.2.3) or a commit hash.

Example fix for a few dependencies:

replace (
-    cloud.google.com/go => cloud.google.com/go upgrade
+    cloud.google.com/go => cloud.google.com/go v0.118.0
-    cloud.google.com/go/bigquery => cloud.google.com/go/bigquery upgrade
+    cloud.google.com/go/bigquery => cloud.google.com/go/bigquery v1.66.0
    // ... fix remaining dependencies similarly
)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0487619 and ce4859f.

⛔ Files ignored due to path filters (2)
  • example/client/go.sum is excluded by !**/*.sum
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (5)
  • example/client/go.mod (1 hunks)
  • example/client/go.mod.default (1 hunks)
  • go.mod (15 hunks)
  • hack/go.mod.default (1 hunks)
  • versions/GO_VERSION (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • versions/GO_VERSION
  • example/client/go.mod.default
⏰ Context from checks skipped due to timeout of 90000ms (107)
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: Run tests for cmd packages
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: Run tests for pkg packages
  • GitHub Check: Run tests for internal packages
  • GitHub Check: grpc-stream
  • GitHub Check: CodeQL
  • GitHub Check: runner / go build
  • GitHub Check: check-format-diff
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build
  • GitHub Check: build / build

hack/go.mod.default Show resolved Hide resolved
example/client/go.mod Show resolved Hide resolved
go.mod Show resolved Hide resolved
go.mod Show resolved Hide resolved
@kmrmt kmrmt requested review from a team, kpango and datelier and removed request for a team January 22, 2025 06:37
@kpango kpango merged commit ecd6ed2 into main Jan 22, 2025
229 of 230 checks passed
@kpango kpango deleted the bugfix/dockerfile/invalid-build-argument branch January 22, 2025 08:45
vdaas-ci pushed a commit that referenced this pull request Jan 22, 2025
* fix go build argument

* update go
kpango pushed a commit that referenced this pull request Jan 23, 2025
* fix go build argument

* update go

Co-authored-by: Kosuke Morimoto <ksk@vdaas.org>
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