GitHub user konstin created a discussion: Does airflow still need UV_HTTP_TIMEOUT?
I'm investigating the defaults of uv wrt to large projects. From https://github.com/search?q=UV_HTTP_TIMEOUT&type=code&p=1, it seems airflow is the main OSS user of setting `UV_HTTP_TIMEOUT` to a non-default value. I've seen that in https://github.com/apache/airflow/pull/38467, airflow added `UV_HTTP_TIMEOUT` (or `UV_REQUEST_TIMEOUT`, as it was initially called). At the point the PR was made, the uv timeout was a full request timeout. After that PR was merged, uv switched to a read timeout, i.e. a timeout only when no data was transferred: UV_REQUEST_TIMEOUT. I was wondering, with the timeout now being a read timeout, does airflow still need to set `UV_HTTP_TIMEOUT`, is the default in uv too low? CC @potiuk GitHub link: https://github.com/apache/airflow/discussions/61205 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
