Hi, I have rebuild my vs-code container with Melta...
# troubleshooting
s
Hi, I have rebuild my vs-code container with Meltano and it is now failing to install airflow. I'm at a bit of a loss as to what is causing this. Any assistance would be much appreciated thank you. The meltano.yml contains the following entry after the install command is run.
Copy code
orchestrators:
  - name: airflow
    pip_url: apache-airflow==2.1.2 --constraint <https://raw.githubusercontent.com/apache/airflow/constraints-2.1.2/constraints-${MELTANO__PYTHON_VERSION}.txt>
And my meltano version is: meltano, version 1.79.1 P.S. I'm not sure if this is helpful but the .devcontainer/Dockerfile contains the following
Copy code
# See here for image contents:
# <https://github.com/microsoft/vscode-dev-containers/tree/v0.187.0/containers/python-3>
FROM <http://mcr.microsoft.com/vscode/devcontainers/python:3.8|mcr.microsoft.com/vscode/devcontainers/python:3.8>

#COPY .env /workspaces/bidw-meltano/.

RUN pipx install meltano
I note that I have re-tried the Meltano Example container from here that was built by AJ. https://github.com/meltano/meltano-cicd-lab-template Then ran
Copy code
meltano add orchestrator airflow
And I still get the same error message, that it can't install Airflow. Any assistance would be much appreciated thank you.
e
Hi @steve_clarke, thanks for reporting! This looks like a similar issue to one I just logged for the SDK. TL;DR: The package
setuptools
which python uses to build and install dependencies, had a release today that makes packages using a legacy
use_2to3
flag fail to install. In the case of the SDK, the offending dependency is
simpleeval
. In the case of Airflow here, it's `flask-openid`: https://github.com/mitsuhiko/flask-openid/blob/master/setup.py#L32.
flask-appbuilder
depends on that package: https://github.com/dpgaspar/Flask-AppBuilder/blob/master/setup.py#L55 and Airflow uses
flask-appbuilder
for its UI. The issue hasn't been reported on Airflow, but I'm sure it'll soon be, so hopefully they can fix it quickly 🤞. cc @aaronsteers
s
Thanks for the update @edgar_ramirez_mondragon. Much appreciated. Is there anything I can do as a work-around for now, or do you think this will be resolved in the next few days?