Yicong-Huang opened a new issue, #4635: URL: https://github.com/apache/texera/issues/4635
### Task Summary Restore `uv pip install --system` in the Build workflow's scala and python jobs. The faster install switch landed in #4521 was accidentally reverted while inlining the binary-license-check changes from #4597. ### Pain point Today both jobs in `build.yml` install python deps with the slower stock `pip`: ``` python -m pip install --upgrade pip if [ -f amber/requirements.txt ]; then pip install -r amber/requirements.txt; fi if [ -f amber/operator-requirements.txt ]; then pip install -r amber/operator-requirements.txt; fi ``` This is the pre-#4521 behaviour; `uv pip install --system` is meaningfully faster on the same dep set and is what the workflow used between #4521 and #4597. ### Proposal Re-apply #4521's payload in `build.yml`: ``` python -m pip install uv if [ -f amber/requirements.txt ]; then uv pip install --system -r amber/requirements.txt; fi if [ -f amber/operator-requirements.txt ]; then uv pip install --system -r amber/operator-requirements.txt; fi ``` …in both the scala job (around line 162) and the python job (around line 264). No behaviour change beyond install speed. ### Priority P2 – Medium ### Task Type - [x] DevOps / Deployment -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
