Commit c7d70d3
Catch RoboflowAPITimeoutError and RoboflowAPIConnectionError in pipeline init (#2285)
Previously these exceptions fell through to the generic Exception handler in
_handle_command, leaving the pipeline subprocess in an unclear state. Now they
surface with explicit error messages and ErrorType.OPERATION_ERROR so operators
can distinguish a network/timeout failure from other init errors.
Related: ROBOFLOW_API_REQUEST_TIMEOUT default added to roboflow-edge build to
prevent indefinite blocking on stale TCP connections after network recovery.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Paweł Pęczek <146137186+PawelPeczek-Roboflow@users.noreply.github.com>1 parent 901fbf2 commit c7d70d3
1 file changed
Lines changed: 18 additions & 0 deletions
Lines changed: 18 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| 23 | + | |
23 | 24 | | |
24 | 25 | | |
| 26 | + | |
25 | 27 | | |
26 | 28 | | |
27 | 29 | | |
| |||
239 | 241 | | |
240 | 242 | | |
241 | 243 | | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
| 251 | + | |
| 252 | + | |
| 253 | + | |
| 254 | + | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
242 | 260 | | |
243 | 261 | | |
244 | 262 | | |
| |||
0 commit comments