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

chore(embeddings): added tests for embeddings #3183

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

StanGirard
Copy link
Collaborator

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Checklist before requesting a review

Please delete options that are not relevant.

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented hard-to-understand areas
  • I have ideally added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Screenshots (if appropriate):

Copy link

vercel bot commented Sep 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
quivrapp ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 10, 2024 5:12pm

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Sep 10, 2024
@dosubot dosubot bot added the area: backend Related to backend functionality or under the /backend directory label Sep 10, 2024
@StanGirard StanGirard changed the title tests(embeddings): added tests for embeddings chore(embeddings): added tests for embeddings Sep 10, 2024
mock_settings.azure_openai_embeddings_url = None

# Create a mock instance for OpenAIEmbeddings
mock_openai_instance = MagicMock()
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why the need for MagicMock here 🤔 . As I understand we are patching the environement to check that we get the correct embedding instance ? Is the openaiembedding instance different from the other cases ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes we read the env key from the env. the others are in the settings

@StanGirard StanGirard merged commit 758e87e into main Sep 11, 2024
7 of 9 checks passed
@StanGirard StanGirard deleted the tests/added-test-embedding branch September 11, 2024 14:00
StanGirard added a commit that referenced this pull request Sep 12, 2024
🤖 I have created a release *beep* *boop*
---


## 0.0.311 (2024-09-12)

## What's Changed
* chore(embeddings): added tests for embeddings by @StanGirard in
#3183
* feat(uptime): check if connection to db works by @StanGirard in
#3199


**Full Changelog**:
v0.0.310...v0.0.311

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: backend Related to backend functionality or under the /backend directory size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants