You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When building an Astro runtime image with the Astro SDK DuckDB submodule the published DuckDB wheel is not used and instead it is compiled locally, which takes many minutes and also requires installing the gcc compiler on the image.
Version
Astro SDK: 1.6.1
Astro runtime: 8.4.0
OS: macOS
To Reproduce
Steps to reproduce the behavior:
Create a new Astro CLI project with astro dev init
Modify requirements.txt to have the line astro-sdk-python[duckdb]==1.6.1
Modify packages.txt to have the line g++ (gcc is required to build the wheel)
Start the Airflow instance with astro dev start
See that it takes ~5 minutes to build the DuckDB wheel
Expected behavior
The published DuckDB wheels to be used instead of building it locally.
The text was updated successfully, but these errors were encountered:
Describe the bug
When building an Astro runtime image with the Astro SDK DuckDB submodule the published DuckDB wheel is not used and instead it is compiled locally, which takes many minutes and also requires installing the
gcc
compiler on the image.Version
To Reproduce
Steps to reproduce the behavior:
astro dev init
requirements.txt
to have the lineastro-sdk-python[duckdb]==1.6.1
packages.txt
to have the lineg++
(gcc
is required to build the wheel)astro dev start
Expected behavior
The published DuckDB wheels to be used instead of building it locally.
The text was updated successfully, but these errors were encountered: