Commit 46b3f25
committed
Do not retry aborted requests and always handle promise rejection
When a network request is aborted through an external signal, it does not make
any sense to retry it.
Also, pending request promises were being (correctly) rejected when the request
failed, but when no one was actually interested in that request, this means that
the rejected promise went unhandled, leading to Node.js issuing an
"UnhandledPromiseRejectionWarning" message to the console.1 parent f205850 commit 46b3f25
1 file changed
+9
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
265 | 265 | | |
266 | 266 | | |
267 | 267 | | |
268 | | - | |
| 268 | + | |
269 | 269 | | |
270 | 270 | | |
271 | 271 | | |
| |||
277 | 277 | | |
278 | 278 | | |
279 | 279 | | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
280 | 285 | | |
281 | 286 | | |
282 | 287 | | |
| |||
376 | 381 | | |
377 | 382 | | |
378 | 383 | | |
379 | | - | |
| 384 | + | |
380 | 385 | | |
381 | 386 | | |
382 | | - | |
| 387 | + | |
383 | 388 | | |
384 | 389 | | |
385 | 390 | | |
| |||
409 | 414 | | |
410 | 415 | | |
411 | 416 | | |
412 | | - | |
| 417 | + | |
413 | 418 | | |
414 | 419 | | |
415 | 420 | | |
| |||
0 commit comments