-
Notifications
You must be signed in to change notification settings - Fork 304
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
docs(samples): explicitly add bq to samples reqs, upgrade grpc to fix bug on m1 #1290
Conversation
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
b94dff5
to
3058a2b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @leahecole, looking at the system test failures, I think we can fix this if we update the required versions in setup.py
(project root) and the constraint files for at least 3.8 and 3.10 in the testing
folder (project root).
Should we also update the grpc requirements in setup.py ? https://github.com/googleapis/python-bigquery/blob/main/setup.py#L32 |
To clarify, the constraint being the grpc version, not the BQ version we also added, right, @loferris? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I can tell from the Kokoro test failures, that seems right to me!! |
@leahecole double-checked, and you probably want to update the |
|
Ok! I'll make those changes. Thanks for the explanation - I've never touched these constraints files before so I wanted to be super sure I was doing the right thing 😁 |
@@ -0,0 +1 @@ | |||
grpcio==1.47.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we remove this line as we still want to test the latest version of grpcio in one of the constraints files.
grpcio==1.47.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we had to add this explicitly to get the system tests (if not, would be happy to delete!!), but I'd suggest I make a follow up issue to clean up the versioning across different versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to approve and merge, but I do want to follow up with @parthea about versioning overall.
SGTM - let me know what you end up deciding! |
… bug on m1 (googleapis#1290) * fix: explicitly add bq to samples reqs, upgrade grpc to fix bug on m1 * update grpc in setup.py * fix: rm 3.6 constraints, add grpcio to 3.7-3.10 constraints
… bug on m1 (googleapis#1290) * fix: explicitly add bq to samples reqs, upgrade grpc to fix bug on m1 * update grpc in setup.py * fix: rm 3.6 constraints, add grpcio to 3.7-3.10 constraints
Related to #1260 and #1262
Can confirm these linked issues definitely happen with M1, but is fixed if you specifically add grpc as an explicit dependency