Does airflow still need UV_HTTP_TIMEOUT?

[konstin]

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

[potiuk]

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?

No idea- we use it because it is added then. Do you think it is save to remove it? It's impossible to say if it is needed without trying it, maybe you can attempt to remove it and run it a couple of times to see if it can be removed? I don't think of other way of checking it. Maybe you have other ideas how we can check it without attempting to remove it ?

[konstin]

I think it's safe to remove it: #62029. If anything should come up, than that's a sign we need to fix something in uv.

[potiuk]

Like really, literally - no idea - it's 1.5 year since it was last touched, so really no idea if anything changed enough to remove it.