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

Add offset shift vector check #2818

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

kmrmt
Copy link
Contributor

@kmrmt kmrmt commented Jan 29, 2025

Description

SSIA

Related Issue

Versions

  • Vald Version: v1.7.16
  • Go Version: v1.23.5
  • 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

  • Tests
    • Enhanced vector comparison logic in end-to-end testing
    • Improved test validation to accommodate different vector arrangements

Copy link
Contributor

coderabbitai bot commented Jan 29, 2025

📝 Walkthrough

Walkthrough

The pull request modifies the GetObject method in the tests/e2e/operation/stream.go file, specifically enhancing the vector comparison logic. The changes introduce a more flexible validation approach by allowing the received vector to match the expected vector or two rotated variations of it. This modification aims to improve the test's robustness by accommodating different arrangements of the same underlying data while maintaining the original method's structure and error handling mechanisms.

Changes

File Change Summary
tests/e2e/operation/stream.go Modified vector comparison logic in GetObject method to support multiple vector arrangements

Possibly related PRs

Suggested labels

type/bug, priority/medium, size/S, area/internal, actions/backport/release/v1.7

Suggested reviewers

  • hlts2
✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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

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 (1)
tests/e2e/operation/stream.go (1)

1151-1155: LGTM! Consider enhancing the error message.

The implementation correctly handles the offset shift vector check by comparing against the original vector and its shifted variations. However, the error message could be more informative.

Consider improving the error message to indicate which variation was expected to match:

-				t.Errorf(
-					"got: %#v, expected: %#v",
-					resp.GetVector(),
-					ds.Train[idx],
-				)
+				t.Errorf(
+					"got: %#v, expected one of:\noriginal: %#v\nshift1: %#v\nshift2: %#v",
+					resp.GetVector(),
+					v,
+					append(v[1:], v[:1]...),
+					append(v[2:], v[:2]...),
+				)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c3b5832 and 07d2ab8.

📒 Files selected for processing (1)
  • tests/e2e/operation/stream.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (41)
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log
  • GitHub Check: E2E test (Stream CRUD) for operator
  • GitHub Check: E2E test (Stream CRUD)
  • GitHub Check: detect-ci-container / detect
  • GitHub Check: dump-contexts-to-log

@vdaas-ci
Copy link
Collaborator

Profile Report

typevald-agent-ngtvald-lb-gatewayvald-discoverervald-manager-index
cpu
heap
other images

@vdaas-ci
Copy link
Collaborator

Profile Report

typevald-agent-ngtvald-lb-gatewayvald-discoverervald-manager-index
cpu
heap
other images

@vankichi vankichi changed the title 🐛 add offset shift vector check Add offset shift vector check Jan 30, 2025
Copy link

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

Deploying vald with  Cloudflare Pages  Cloudflare Pages

Latest commit: 586b933
Status: ✅  Deploy successful!
Preview URL: https://23c8dd51.vald.pages.dev
Branch Preview URL: https://bugfix-e2e-add-getobject-off.vald.pages.dev

View logs

@kmrmt kmrmt requested review from a team, vankichi and datelier and removed request for a team January 31, 2025 04:16
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.

3 participants