Bump grpcio to v1.64 to fix build error #6170
Open
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 ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6170 +/- ##
==========================================
- Coverage 54.92% 54.30% -0.63%
==========================================
Files 150 150
Lines 14125 14125
==========================================
- Hits 7758 7670 -88
- Misses 6367 6455 +88
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
We have seen errors in tests for newer versions of |
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.
Goals:
Hi, the latest version of jina installed via poetry fails due to its dependency,
grpcio v1.57.0, failing to build on x86_64 Linux w/ Python v3.12.3. A Google search brought me to google/bumble#459, which hinted that the solution might be to upgrade to v1.64.0. Sure enough, changing the dependency version fixes the build.