gopidesupavan commented on PR #61794: URL: https://github.com/apache/airflow/pull/61794#issuecomment-3895637541
> > ``` > > × No solution found when resolving dependencies for split (markers: > > │ python_full_version >= '3.14' and sys_platform == 'win32'): > > ╰─▶ Because s3fs==2026.2.0 depends on fsspec==2026.2.0 and fsspec==2026.1.0, > > we can conclude that s3fs>=2026.1.0 depends on fsspec>=2026.1.0. (1) > > hint: Pre-releases are available for `grpcio-status` in the requested > > range (e.g., 1.78.0rc2), but pre-releases weren't enabled (try: > > `--prerelease=allow`) > > ``` > > > > > > > > > > > > > > > > > > > > > > > > The latest pydantic-ai package version isn’t resolving but version 0.0.5 resolving, which is quite outdated and doesn’t include the newer features or model providers. > > I’m scratching my head at this point. Any help would be greatly appreciated.. > > I ran into a similar issue issue when testing locally. For me the chain was pydantic-ai (new versino) → logfire → opentelemetry-sdk, which conflicts with Airflow's own opentelemetry pins. With pydantic 0.0.5 there is a _griffe version incompatibility. > > _Might be worth checking if pydantic-ai-slim_ > > https://pypi.org/project/pydantic-ai-slim/ yup, still the same isuue. ``` (airflow) gopidesupavan@Mac airflow % uv sync --all-packages × No solution found when resolving dependencies for split (markers: python_full_version == '3.12.*'): ╰─▶ Because only the following versions of opentelemetry-exporter-otlp are available: opentelemetry-exporter-otlp<=1.27.0 opentelemetry-exporter-otlp==1.28.0 opentelemetry-exporter-otlp==1.28.1 opentelemetry-exporter-otlp==1.28.2 opentelemetry-exporter-otlp==1.29.0 opentelemetry-exporter-otlp==1.30.0 opentelemetry-exporter-otlp==1.31.0 opentelemetry-exporter-otlp==1.31.1 opentelemetry-exporter-otlp==1.32.0 opentelemetry-exporter-otlp==1.32.1 opentelemetry-exporter-otlp==1.33.0 opentelemetry-exporter-otlp==1.33.1 opentelemetry-exporter-otlp==1.34.0 opentelemetry-exporter-otlp==1.34.1 opentelemetry-exporter-otlp==1.35.0 opentelemetry-exporter-otlp==1.36.0 opentelemetry-exporter-otlp==1.37.0 opentelemetry-exporter-otlp==1.38.0 opentelemetry-exporter-otlp==1.39.0 opentelemetry-exporter-otlp==1.39.1 and opentelemetry-exporter-otlp==1.28.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.28.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.28.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.28.0. And because opentelemetry-exporter-otlp-proto-grpc==1.28.0 depends on opentelemetry-proto==1.28.0 and opentelemetry-exporter-otlp==1.28.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.28.1, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.28.2, opentelemetry-exporter-otlp-proto-grpc!=1.28.1, opentelemetry-proto!=1.28.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.28.1 depends on opentelemetry-proto==1.28.1 and opentelemetry-exporter-otlp==1.28.2 depends on opentelemetry-exporter-otlp-proto-grpc==1.28.2, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.29.0, opentelemetry-exporter-otlp-proto-grpc!=1.28.2, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.28.1 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.28.2 depends on opentelemetry-proto==1.28.2 and opentelemetry-exporter-otlp==1.29.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.29.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.30.0, opentelemetry-exporter-otlp-proto-grpc!=1.29.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.28.2 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.29.0 depends on opentelemetry-proto==1.29.0 and opentelemetry-exporter-otlp==1.30.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.30.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.31.0, opentelemetry-exporter-otlp-proto-grpc!=1.30.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.29.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.30.0 depends on opentelemetry-proto==1.30.0 and opentelemetry-exporter-otlp==1.31.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.31.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.31.1, opentelemetry-exporter-otlp-proto-grpc!=1.31.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.30.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.31.0 depends on opentelemetry-proto==1.31.0 and opentelemetry-exporter-otlp==1.31.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.31.1, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.32.0, opentelemetry-exporter-otlp-proto-grpc!=1.31.1, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.31.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.31.1 depends on opentelemetry-proto==1.31.1 and opentelemetry-exporter-otlp==1.32.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.32.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.32.1, opentelemetry-exporter-otlp-proto-grpc!=1.32.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.31.1 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.32.0 depends on opentelemetry-proto==1.32.0 and opentelemetry-exporter-otlp==1.32.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.32.1, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.33.0, opentelemetry-exporter-otlp-proto-grpc!=1.32.1, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.32.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.32.1 depends on opentelemetry-proto==1.32.1 and opentelemetry-exporter-otlp==1.33.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.33.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.33.1, opentelemetry-exporter-otlp-proto-grpc!=1.33.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.32.1 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.33.0 depends on opentelemetry-proto==1.33.0 and opentelemetry-exporter-otlp==1.33.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.33.1, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.34.0, opentelemetry-exporter-otlp-proto-grpc!=1.33.1, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.33.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.33.1 depends on opentelemetry-proto==1.33.1 and opentelemetry-exporter-otlp==1.34.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.34.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.34.1, opentelemetry-exporter-otlp-proto-grpc!=1.34.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.33.1 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.34.0 depends on opentelemetry-proto==1.34.0 and opentelemetry-exporter-otlp==1.34.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.34.1, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.35.0, opentelemetry-exporter-otlp-proto-grpc!=1.34.1, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.34.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.34.1 depends on opentelemetry-proto==1.34.1 and opentelemetry-exporter-otlp==1.35.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.35.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.36.0, opentelemetry-exporter-otlp-proto-grpc!=1.35.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.34.1 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.35.0 depends on opentelemetry-proto==1.35.0 and opentelemetry-exporter-otlp==1.36.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.36.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.37.0, opentelemetry-exporter-otlp-proto-grpc!=1.36.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.35.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.36.0 depends on opentelemetry-proto==1.36.0 and opentelemetry-exporter-otlp==1.37.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.37.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.38.0, opentelemetry-exporter-otlp-proto-grpc!=1.37.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.36.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.37.0 depends on opentelemetry-proto==1.37.0 and opentelemetry-exporter-otlp==1.38.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.38.0, we can conclude that opentelemetry-exporter-otlp>1.27.0,<1.39.0, opentelemetry-exporter-otlp-proto-grpc!=1.38.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.37.0 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.38.0 depends on opentelemetry-proto==1.38.0 and opentelemetry-exporter-otlp==1.39.1 depends on opentelemetry-exporter-otlp-proto-grpc==1.39.1, we can conclude that all of: opentelemetry-exporter-otlp>1.27.0,<1.39.0 opentelemetry-exporter-otlp>1.39.0 , opentelemetry-exporter-otlp-proto-grpc!=1.39.1, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.38.0 are incompatible. And because opentelemetry-exporter-otlp==1.39.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.39.0 and opentelemetry-exporter-otlp-proto-grpc==1.39.1 depends on opentelemetry-proto==1.39.1, we can conclude that opentelemetry-exporter-otlp>1.27.0, opentelemetry-exporter-otlp-proto-grpc!=1.39.0, all of: opentelemetry-proto<1.28.0 opentelemetry-proto>1.38.0,<1.39.1 are incompatible. And because opentelemetry-exporter-otlp-proto-grpc==1.39.0 depends on opentelemetry-proto==1.39.0 and apache-airflow-core depends on opentelemetry-exporter-otlp>=1.27.0, we can conclude that opentelemetry-exporter-otlp!=1.27.0, opentelemetry-proto<1.28.0, apache-airflow-core[all] are incompatible. (1) Because only the following versions of apache-beam are available: apache-beam<=2.60.0 apache-beam==2.61.0 apache-beam==2.62.0 apache-beam==2.63.0 apache-beam==2.64.0 apache-beam==2.65.0 apache-beam==2.66.0 apache-beam==2.67.0 apache-beam==2.68.0 apache-beam==2.69.0 apache-beam==2.70.0 apache-beam==2.71.0 and apache-beam==2.60.0 depends on one of: protobuf>=3.20.3,<4.0.dev0 protobuf>=4.22.dev0,<4.22.0 protobuf>4.22.0,<4.23.dev0 protobuf>=4.25.dev0,<4.26.0 we can conclude that apache-beam>=2.60.0,<2.61.0 depends on one of: protobuf>=3.20.3,<4.0.dev0 protobuf>=4.22.dev0,<4.22.0 protobuf>4.22.0,<4.23.dev0 protobuf>=4.25.dev0,<4.26.0 And because apache-beam>=2.61.0,<=2.65.0 depends on one of: grpcio>=1.33.1,<1.48.0 grpcio>1.48.0,<1.59.dev0 grpcio>=1.62.dev0,<1.62.0 grpcio>1.62.1,<1.66.0 and one of: grpcio{python_full_version < '3.13'}>=1.33.1,<1.48.0 grpcio{python_full_version < '3.13'}>1.48.0,<1.59.dev0 grpcio{python_full_version < '3.13'}>=1.62.dev0,<1.62.0 grpcio{python_full_version < '3.13'}>1.62.1,<1.66.0 we can conclude that apache-beam>=2.60.0, all of: grpcio<1.33.1 grpcio==1.48.0 grpcio>=1.59.dev0,<1.62.dev0 grpcio>=1.62.0,<=1.62.1 grpcio>=1.66.0 , all of: protobuf<3.20.3 protobuf>=4.0.dev0,<4.22.dev0 protobuf==4.22.0 protobuf>=4.23.dev0,<4.25.dev0 protobuf>=4.26.0 are incompatible. (2) Because only the following versions of yandexcloud{python_full_version < '3.13'} are available: yandexcloud{python_full_version < '3.13'}<=0.328.0 yandexcloud{python_full_version < '3.13'}==0.329.0 yandexcloud{python_full_version < '3.13'}==0.330.0 yandexcloud{python_full_version < '3.13'}==0.331.0 yandexcloud{python_full_version < '3.13'}==0.332.0 yandexcloud{python_full_version < '3.13'}==0.333.0 yandexcloud{python_full_version < '3.13'}==0.334.0 yandexcloud{python_full_version < '3.13'}==0.335.0 yandexcloud{python_full_version < '3.13'}==0.336.0 yandexcloud{python_full_version < '3.13'}==0.337.0 yandexcloud{python_full_version < '3.13'}==0.338.0 yandexcloud{python_full_version < '3.13'}==0.339.0 yandexcloud{python_full_version < '3.13'}==0.340.0 yandexcloud{python_full_version < '3.13'}==0.341.0 yandexcloud{python_full_version < '3.13'}==0.342.0 yandexcloud{python_full_version < '3.13'}==0.343.0 yandexcloud{python_full_version < '3.13'}==0.344.0 yandexcloud{python_full_version < '3.13'}==0.345.0 yandexcloud{python_full_version < '3.13'}==0.346.0 yandexcloud{python_full_version < '3.13'}==0.347.0 yandexcloud{python_full_version < '3.13'}==0.348.0 yandexcloud{python_full_version < '3.13'}==0.349.0 yandexcloud{python_full_version < '3.13'}==0.350.0 yandexcloud{python_full_version < '3.13'}==0.351.0 yandexcloud{python_full_version < '3.13'}==0.352.0 yandexcloud{python_full_version < '3.13'}==0.353.0 yandexcloud{python_full_version < '3.13'}==0.354.0 yandexcloud{python_full_version < '3.13'}==0.355.0 yandexcloud{python_full_version < '3.13'}==0.356.0 yandexcloud{python_full_version < '3.13'}==0.357.0 yandexcloud{python_full_version < '3.13'}==0.358.0 yandexcloud{python_full_version < '3.13'}==0.359.0 yandexcloud{python_full_version < '3.13'}==0.360.0 yandexcloud{python_full_version < '3.13'}==0.361.0 yandexcloud{python_full_version < '3.13'}==0.362.0 yandexcloud{python_full_version < '3.13'}==0.363.0 yandexcloud{python_full_version < '3.13'}==0.364.0 yandexcloud{python_full_version < '3.13'}==0.365.0 yandexcloud{python_full_version < '3.13'}==0.366.0 yandexcloud{python_full_version < '3.13'}==0.367.0 yandexcloud{python_full_version < '3.13'}==0.368.0 yandexcloud{python_full_version < '3.13'}==0.369.0 yandexcloud{python_full_version < '3.13'}==0.370.0 yandexcloud{python_full_version < '3.13'}==0.371.0 yandexcloud{python_full_version < '3.13'}==0.372.0 yandexcloud{python_full_version < '3.13'}==0.373.0 yandexcloud{python_full_version < '3.13'}==0.374.0 yandexcloud{python_full_version < '3.13'}==0.375.0 yandexcloud{python_full_version < '3.13'}==0.376.0 yandexcloud{python_full_version < '3.13'}==0.377.0 and yandexcloud{python_full_version < '3.13'}>=0.329.0,<=0.333.0 was yanked (reason: https://github.com/yandex-cloud/python-sdk/issues/138), we can conclude that yandexcloud{python_full_version < '3.13'}>=0.329.0,<=0.333.0 cannot be used. And because yandexcloud>=0.334.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.336.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.336.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.338.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.338.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.340.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.340.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.342.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.342.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.344.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.344.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.346.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.346.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.348.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.348.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.350.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.350.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.352.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.352.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.354.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.354.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.356.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.356.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.358.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.358.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.360.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.360.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.362.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.362.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.364.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.364.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.366.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.366.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.368.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.368.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.370.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.370.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.372.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.372.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.374.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.374.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0,<0.376.0 depends on grpcio>=1.68.1. And because yandexcloud>=0.376.0 depends on grpcio>=1.68.1 and grpcio>=1.68.1, we can conclude that yandexcloud{python_full_version < '3.13'}>0.328.0 depends on grpcio>=1.68.1. (3) And because we know from (2) that apache-beam>=2.60.0, all of: grpcio<1.33.1 grpcio==1.48.0 grpcio>=1.59.dev0,<1.62.dev0 grpcio>=1.62.0,<=1.62.1 grpcio>=1.66.0 , all of: protobuf<3.20.3 protobuf>=4.0.dev0,<4.22.dev0 protobuf==4.22.0 protobuf>=4.23.dev0,<4.25.dev0 protobuf>=4.26.0 are incompatible, we can conclude that apache-beam>=2.60.0, all of: protobuf<3.20.3 protobuf>=4.0.dev0,<4.22.dev0 protobuf==4.22.0 protobuf>=4.23.dev0,<4.25.dev0 protobuf>=4.26.0 , yandexcloud{python_full_version < '3.13'}>0.328.0 are incompatible. And because yandexcloud==0.328.0 depends on protobuf>=4.25.3,<5 and opentelemetry-proto>=1.28.0,<=1.34.1 depends on protobuf>=5.0,<6.0, we can conclude that apache-beam>=2.60.0, opentelemetry-proto>=1.28.0,<=1.34.1, yandexcloud{python_full_version < '3.13'}>=0.328.0 are incompatible. (4) Because only the following versions of apache-beam are available: apache-beam<=2.60.0 apache-beam==2.61.0 apache-beam==2.62.0 apache-beam==2.63.0 apache-beam==2.64.0 apache-beam==2.65.0 apache-beam==2.66.0 apache-beam==2.67.0 apache-beam==2.68.0 apache-beam==2.69.0 apache-beam==2.70.0 apache-beam==2.71.0 and apache-beam==2.60.0 depends on one of: protobuf>=3.20.3,<4.0.dev0 protobuf>=4.22.dev0,<4.22.0 protobuf>4.22.0,<4.23.dev0 protobuf>=4.25.dev0,<4.26.0 we can conclude that apache-beam>=2.60.0,<2.61.0 depends on one of: protobuf>=3.20.3,<4.0.dev0 protobuf>=4.22.dev0,<4.22.0 protobuf>4.22.0,<4.23.dev0 protobuf>=4.25.dev0,<4.26.0 And because apache-beam>=2.61.0,<=2.65.0 depends on one of: grpcio>=1.33.1,<1.48.0 grpcio>1.48.0,<1.59.dev0 grpcio>=1.62.dev0,<1.62.0 grpcio>1.62.1,<1.66.0 and one of: grpcio{python_full_version < '3.13'}>=1.33.1,<1.48.0 grpcio{python_full_version < '3.13'}>1.48.0,<1.59.dev0 grpcio{python_full_version < '3.13'}>=1.62.dev0,<1.62.0 grpcio{python_full_version < '3.13'}>1.62.1,<1.66.0 we can conclude that apache-beam>=2.60.0, all of: grpcio<1.33.1 grpcio==1.48.0 grpcio>=1.59.dev0,<1.62.dev0 grpcio>=1.62.0,<=1.62.1 grpcio>=1.66.0 , all of: protobuf<3.20.3 protobuf>=4.0.dev0,<4.22.dev0 protobuf==4.22.0 protobuf>=4.23.dev0,<4.25.dev0 protobuf>=4.26.0 are incompatible. And because we know from (3) that yandexcloud{python_full_version < '3.13'}>0.328.0 depends on grpcio>=1.68.1, we can conclude that apache-beam>=2.60.0, all of: protobuf<3.20.3 protobuf>=4.0.dev0,<4.22.dev0 protobuf==4.22.0 protobuf>=4.23.dev0,<4.25.dev0 protobuf>=4.26.0 , yandexcloud{python_full_version < '3.13'}>0.328.0 are incompatible. And because yandexcloud==0.328.0 depends on protobuf>=4.25.3,<5 and opentelemetry-proto>=1.35.0 depends on protobuf>=5.0, we can conclude that apache-beam>=2.60.0, opentelemetry-proto>=1.35.0, yandexcloud{python_full_version < '3.13'}>=0.328.0 are incompatible. And because we know from (4) that apache-beam>=2.60.0, opentelemetry-proto>=1.28.0,<=1.34.1, yandexcloud{python_full_version < '3.13'}>=0.328.0 are incompatible, we can conclude that apache-beam>=2.60.0, opentelemetry-proto>=1.28.0, yandexcloud{python_full_version < '3.13'}>=0.328.0 are incompatible. And because apache-airflow-providers-yandex depends on yandexcloud{python_full_version < '3.13'}>=0.328.0, we can conclude that apache-airflow-providers-yandex, apache-beam>=2.60.0, opentelemetry-proto>=1.28.0 are incompatible. And because we know from (1) that opentelemetry-exporter-otlp!=1.27.0, opentelemetry-proto<1.28.0, apache-airflow-core[all] are incompatible, we can conclude that apache-airflow-providers-yandex, apache-beam>=2.60.0, opentelemetry-exporter-otlp!=1.27.0, apache-airflow-core[all] are incompatible. And because apache-airflow-providers-apache-beam depends on apache-beam{python_full_version < '3.13'}>=2.60.0, we can conclude that apache-airflow-providers-apache-beam, apache-airflow-providers-yandex, opentelemetry-exporter-otlp!=1.27.0, apache-airflow-core[all] are incompatible. (5) Because opentelemetry-sdk==1.27.0 depends on opentelemetry-api==1.27.0 and only the following versions of opentelemetry-sdk are available: opentelemetry-sdk<=1.27.0 opentelemetry-sdk>1.28.dev0 we can conclude that opentelemetry-sdk>=1.27.0,<1.28.dev0 depends on opentelemetry-api==1.27.0. And because opentelemetry-exporter-otlp-proto-grpc==1.27.0 depends on opentelemetry-sdk>=1.27.0,<1.28.dev0 and opentelemetry-exporter-otlp==1.27.0 depends on opentelemetry-exporter-otlp-proto-grpc==1.27.0, we can conclude that opentelemetry-api!=1.27.0, opentelemetry-exporter-otlp==1.27.0, all versions of opentelemetry-exporter-otlp-proto-grpc are incompatible. And because we know from (5) that apache-airflow-providers-apache-beam, apache-airflow-providers-yandex, opentelemetry-exporter-otlp!=1.27.0, apache-airflow-core[all] are incompatible, we can conclude that apache-airflow-providers-yandex, opentelemetry-api!=1.27.0, apache-airflow-core[all], apache-airflow-providers-apache-beam[google] are incompatible. And because pydantic-ai-slim==1.58.0 depends on opentelemetry-api>=1.28.0, we can conclude that apache-airflow-providers-yandex, pydantic-ai-slim==1.58.0, apache-airflow-core[all], apache-airflow-providers-apache-beam[google] are incompatible. And because only pydantic-ai-slim<=1.58.0 is available and apache-airflow-providers-common-ai depends on pydantic-ai-slim>=1.58.0, we can conclude that apache-airflow-providers-common-ai, apache-airflow-providers-yandex, apache-airflow-core[all], apache-airflow-providers-apache-beam[google] are incompatible. And because your workspace requires apache-airflow-core[all] and apache-airflow-providers-apache-beam[google], we can conclude that your workspace's requirements, apache-airflow-providers-yandex, apache-airflow-providers-common-ai[common-compat] are incompatible. And because your workspace requires apache-airflow-providers-common-ai[common-compat] and apache-airflow-providers-yandex, we can conclude that your workspace's requirements are unsatisfiable. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
