samypr100 757f8e2f60 feat: improved msg for network timeouts (#1961) ... ## Summary Closes #1922 When a timeout occurs, it hints to the user to configure the `UV_HTTP_TIMEOUT` env var. Before ``` error: Failed to download distributions Caused by: Failed to fetch wheel: torch==2.2.0 Caused by: Failed to extract source distribution Caused by: request or response body error: operation timed out Caused by: operation timed out ``` After ``` error: Failed to download distributions Caused by: Failed to fetch wheel: torch==2.2.0 Caused by: Failed to extract source distribution Caused by: Failed to download distribution due to network timeout. Try increasing UV_HTTP_TIMEOUT. ``` ## Test Plan <!-- How was it tested? --> Wasn't sure if we'd want a test. If we do, is there a existing mechanism or preferred approach to force a timeout to occur in tests? Maybe set the timeout to 1 and add torch as an install check (although it's possible that could become flaky)?		2024-02-25 21:13:28 +00:00
..
src	feat: improved msg for network timeouts (#1961)	2024-02-25 21:13:28 +00:00
Cargo.toml	Rename to uv (#1302)	2024-02-15 11:19:46 -06:00