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 Couchbase VectorDB Support #3525

Merged

Conversation

lokesh-couchbase
Copy link
Contributor

@lokesh-couchbase lokesh-couchbase commented Sep 13, 2024

Why are these changes needed?

Couchbase is a NoSQL Key-Value Based Database. Couchbase has recently added support for Vector Search. We would like to add support for Couchbase as a vectorDB in autogen.

Checks

@lokesh-couchbase
Copy link
Contributor Author

@microsoft-github-policy-service agree company="Couchbase"

Copy link
Member

@jackgerrits jackgerrits left a comment

Choose a reason for hiding this comment

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

Thanks!

@jackgerrits
Copy link
Member

@lokesh-couchbase can you fix the code formatting check?

@lokesh-couchbase
Copy link
Contributor Author

HI @jackgerrits , I have fixed the formatting issues
Thanks

@jackgerrits
Copy link
Member

Thank you!

Copy link

gitguardian bot commented Sep 25, 2024

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
12853598 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
10404693 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
12853599 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
10404694 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
12853601 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
10404696 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
10422482 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
12853602 Triggered Generic High Entropy Secret e42837d test/oai/test_utils.py View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

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.

2 participants