fix: fix docarray at v1 #911
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #911 +/- ##
===========================================
- Coverage 82.73% 71.61% -11.13%
===========================================
Files 23 23
Lines 1564 1564
===========================================
- Hits 1294 1120 -174
- Misses 270 444 +174
Flags with carried forward coverage won't be shown. Click here to find out more. see 4 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to prevent the installation of DocArrayV2, as we have encountered some compatibility issues that require further investigation. While this solution is temporary, it will allow us to ensure that our codebase remains stable and free from potential conflicts.
After conducting a thorough investigation of the compatibility of DocArrayV2, we will determine the best course of action moving forward. Until then, we appreciate your patience and understanding as we work to maintain the integrity of our codebase.