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

making dagster grpc requirements more friendly with other package deps #3085

Merged
merged 1 commit into from
Oct 15, 2020

Conversation

jmo-qap
Copy link
Contributor

@jmo-qap jmo-qap commented Oct 12, 2020

@alangenfeld
Copy link
Member

Thanks a ton for digging in here and following up on your well crafted issue with a well crafted PR. This looks good to me, I will double check with some other folks on the team and likely merge this assuming it clears buildkite (you can ignore the current azure failures).

@@ -68,8 +68,8 @@ def get_version():
# core (not explicitly expressed atm)
"alembic>=1.2.1",
"croniter>=0.3.34",
"grpcio==1.30.0", # pinned so that code generated by grpc will work
"protobuf==3.12.4", # pinned so that code generated by grpc will work
"grpcio>=1.32.0", # ensure version we require is >= that with which we generated the grpc code (set in dev-requirements)
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it asking too much to have a test which checks this against dev-requirements?

@alangenfeld alangenfeld merged commit 8b247e9 into dagster-io:master Oct 15, 2020
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.

dagster grpcio pinning is incompatible with pulumi grpcio pinning
3 participants