Abdelkader Midani

I have the same issue, 4.0.x works fine 4.1.x generate this error, it's like the ramdom port ${wiremock.server.port} is the default one in the setup method (@BeforeAll)

I have the same issue with different ingestion sources, found this when I took a look at the pod's logs There's a timeout when installing packages, in my case we...

> [@amidani-inovany](https://github.com/amidani-inovany) can you set the custom env variable on the ingestion ui at the advanced section? -> https://docs.datahub.com/docs/ui-ingestion#advanced-configuration-options @treff7es thanks for the hint, works well as a temp workaround

I just got a new issue related to this, the PIP_GLOBAL_EXTRA_PACKAGES is not picked up by the created venv, in my case I have installed the package from a private...

As a work around I downgraded acryl-executor when building datahug-actions image, I added this in the Dockerfile: `RUN uv pip install acryl-executor==0.2.2`