potiuk commented on PR #48733:
URL: https://github.com/apache/airflow/pull/48733#issuecomment-2788244360

   Actually, the command was right but the parameter defintion was missing. 
   
   Currently (and that might not be the best) we are using TEST_TYPE to 
determine **WHICH** provider should be used to downgrade the lowest 
dependencies to.
   
   ```bash
   function check_force_lowest_dependencies() {
       if [[ ${FORCE_LOWEST_DEPENDENCIES=} != "true" ]]; then
           return
       fi
       if [[ ${TEST_TYPE=} =~ Providers\[.*\] ]]; then
           local provider_id
           # shellcheck disable=SC2001
           provider_id=$(echo "${TEST_TYPE}" | sed 's/Providers\[\(.*\)\]/\1/')
           echo
           echo "${COLOR_BLUE}Forcing dependencies to lowest versions for 
provider: ${provider_id}${COLOR_RESET}"
           echo
           if ! /opt/airflow/scripts/in_container/is_provider_excluded.py 
"${provider_id}"; then
               echo
               echo "S${COLOR_YELLOW}Skipping ${provider_id} provider check on 
Python ${PYTHON_MAJOR_MINOR_VERSION}!${COLOR_RESET}"
               echo
               exit 0
           fi
           cd "${AIRFLOW_SOURCES}/providers/${provider_id/.//}" || exit 1
           uv sync --resolution lowest-direct
       else
           echo
           echo "${COLOR_BLUE}Forcing dependencies to lowest versions for 
Airflow.${COLOR_RESET}"
           echo
           cd "${AIRFLOW_SOURCES}/airflow-core"
           uv sync --resolution lowest-direct
       fi
   }
   ```
   
   So the problem was really missing --test-type option in breeze shell.
   
   But yes - it's not intuitive so let me describe how to manually do the same 
- especially that we have caching as of a few days mounted from host that will 
speed up uv sync command run manually inside the container.


-- 
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]

Reply via email to