uranusjr opened a new issue #14994: URL: https://github.com/apache/airflow/issues/14994
Currently all PRs have their CI failing during the *Check if CI image build is needed* stage because `pip check` fails with ``` apache-beam 2.28.0 has requirement dill<0.3.2,>=0.3.1.1, but you have dill 0.3.3. ``` The source of the conflict is simple; Airflow itself declares `dill>=0.2.2, <0.4`, but `apache-beam[gcp]` (pulled in by extra) declares `>=0.3.1.1,<0.3.2`. The CI is currently using pip’s legacy resolver, which naively chooses in dill 0.3.3 when it seems the initial requirement in `apache-airflow` to cause the conflict. The thing I’ve *not* figured out, however, is why the CI worked previously. Neither `apache-airflow` and `apache-beam` have changed this particular dependency declaration for quite a long time, and a similar conflict should have occured long before this. As for a fix, the simplest solution would be to pin `apache-airflow`’s `dill` dependency to `<0.3.2`. Or switch to pip’s new resolver, which can correctly install `apache-airflow[all]` as of pip 21.0.1 from my test run. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
