amoghrajesh commented on PR #64148:
URL: https://github.com/apache/airflow/pull/64148#issuecomment-4140308340
The failures here are unrelated, like this:
```python
Provider yandex is not excluded.
Ignoring existing lockfile due to change in resolution mode: `highest` vs.
`lowest-direct`
warning: The direct dependency `setuptools` is unpinned. Consider setting
a lower bound when using `--resolution lowest` or `--resolution lowest-direct`
to avoid using outdated versions.
warning: The direct dependency `pyspark` is unpinned. Consider setting a
lower bound when using `--resolution lowest` or `--resolution lowest-direct` to
avoid using outdated versions.
warning: The direct dependency `pydantic-ai-slim` is unpinned. Consider
setting a lower bound when using `--resolution lowest` or `--resolution
lowest-direct` to avoid using outdated versions.
warning: The direct dependency `pytest` is unpinned. Consider setting a
lower bound when using `--resolution lowest` or `--resolution lowest-direct` to
avoid using outdated versions.
Resolved 928 packages in 8.26s
Building apache-airflow-providers-yandex @
file:///opt/airflow/providers/yandex
Downloading yandexcloud (5.4MiB)
Built apache-airflow-providers-yandex @
file:///opt/airflow/providers/yandex
Downloaded yandexcloud
× Failed to download and build `grpcio-tools==1.71.2`
├─▶ Failed to acquire lock on the distribution cache
├─▶ Could not acquire lock
╰─▶ Timeout (300s) when waiting for lock on
`/root/.cache/uv/sdists-v9/pypi/grpcio-tools/1.71.2` at
`/root/.cache/uv/sdists-v9/pypi/grpcio-tools/1.71.2/.lock`, is
another
uv process running? You can set `UV_LOCK_TIMEOUT` to increase the
timeout.
help: `grpcio-tools` (v1.71.2) was included because
`apache-airflow-providers-yandex` (v4.4.1) depends on `yandexcloud`
(v0.376.0) which depends on `grpcio-tools`
```
--
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]
