It looks like

grpcio

versions are incompatible with latest

dagster

and

gcsfs

which we're using in conjunction with

upath

. Pip-compile giving me this error:

grpcio>=1.51.3 (from grpcio-status==1.51.3->google-api-core[grpc]==2.11.0->google-cloud-storage==2.7.0->gcsfs==2023.1.0->my_project (pyproject.toml))
grpcio<1.48.1,>=1.32.0 (from dagster==1.1.19->my_project (pyproject.toml))

Should I open a support ticket?

We're working closely with the grpc team on getting that pin removed - it's due to an upstream issue that's affecting us and a number of other libraries

Okay, that makes sense. I'll see if I can downgrade gcsfs for a less agressive minimum.

The issue is here: https://github.com/grpc/grpc/issues/31885 - hoping we can get unpinned soon

It looks like

dagster-gcp

is also requiring an incompatible version via

google-cloud-storage

grpcio>=1.51.3 (from grpcio-status==1.51.3->google-api-core[grpc]==2.11.0->google-cloud-storage==2.7.0->dagster-gcp==0.17.19->my-project (pyproject.toml))

Should

dagster-gcp

stay pinned to an earlier version until dagster can be compatible?

Hm I don't see any specific pins in dagster-gcp, here's the relevant part of the setup.py

install_requires=[
        "db-dtypes",  # Required as per <https://github.com/googleapis/python-bigquery/issues/1188>
        "google-api-python-client",
        "google-cloud-bigquery",
        "google-cloud-storage",
        "oauth2client",
    ],

hm, for some reason pip-compile has locked in on a specific version of

google-cloud-storage

.

Hm, odd - I'm not deeply familiar with pip-compile but if you have a sample command that's hitting issues we could see if we can reproduce the problem

thanks, I'll let you know