Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-05 Thread via GitHub
potiuk commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2040175237 :upside_down_face: -- 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.

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-05 Thread via GitHub
notatallshaw commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2040164554 > Agree. `uv` has the big advntage for now that it does not `have` to support all those legacy cases - far less number of people will complain if something won't work :)

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-05 Thread via GitHub
potiuk commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2040039543 Good input. Thanks @notatallshaw :) > In general the behavior of uv's resolution algorithm (powered by pugrub-rs) has a tendency to want to exchaust all possible versions of a

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-05 Thread via GitHub
notatallshaw commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2039907669 I wasn't able to quickly reproduce this, but some flags that help with reproducing these issues for uv in the future are `--dry-run` to not pollute your environment, `--reinstall`

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-05 Thread via GitHub
potiuk commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2039233516 It's been very specific - an I am not sure if it is constrantly reproducible - this is the nature of dependency resolving that it constantly changes, depending on what is currrently

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-04 Thread via GitHub
hussein-awala commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2038405070 I could not reproduce it with UV 0.1.29 and the command you provided in the issue created in UV project, but I didn't try with 0.1.28: ```bash (airflow) ➜ airflow

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-04 Thread via GitHub
potiuk merged PR #38753: URL: https://github.com/apache/airflow/pull/38753 -- 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:

Re: [PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-04 Thread via GitHub
potiuk commented on PR #38753: URL: https://github.com/apache/airflow/pull/38753#issuecomment-2037807012 Example problem from v2-9-test it solves: https://github.com/apache/airflow/actions/runs/8555464849/job/23446007205#step:10:3693 ``` #64 6.287 Caused by: Couldn't parse

[PR] Add google-cloud-bigquery as explicit google-provider dependency [airflow]

2024-04-04 Thread via GitHub
potiuk opened a new pull request, #38753: URL: https://github.com/apache/airflow/pull/38753 The new Google Cloud Bigquery released few days ago, caused some weird backtracking UV issue for Python 3.11 builds where airflow uses PyPI providers in PROD image builds. UV seems to fail on really