The GitHub Actions job "Tests" on airflow.git has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
8156e7dab0bb994b7f22dc763c632b7ecf3d958b / Jarek Potiuk <[email protected]>
Fix few issues with constraints generation broken by moving providers

As part of #46045 we are moving all providers to the new structure,
each with it's own pyproject.toml. However we noticed that constraint
generation is somewhat broken during the move:

* providers moved to the new structure disappeared from pypi constraints
* http provider in SOME PRs started to appear in "source constraints"

Both should not happen:

* pypi constraints should contain all providers (latest versions in
  PyPI)
* source providers should contain no providers - only their dependencies

There are two reasons for those two issues, and this PR fixes both:

1) The PyPI providers were removed because `uv pip install .` without
   editable flag is currently - pretty unexpectedly - installing
   local workspaced providers rather than install them from PyPI and
   there are no controls to disable it.

   Workaround for that is that during constraint generation we
   remove temporarily all providers from workspace definition in the
   pyproject.toml - this way providers are installed from PyPI.
   Feature request to handle it has been raised in the
   https://github.com/astral-sh/uv/issues/10991

2) The http provider was added to the constraint in PRs where
   the http provider is a required dependency (for example in
   discord provider). Since the http provider is not yet
   migrated, discord installation in workspace will pull it
   from PyPI rather than from the local workspace.

   This has been fixed by simply migrating the http provider
   to the new structure,

Report URL: https://github.com/apache/airflow/actions/runs/12994220842

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to