041dedb86e
Retrying seems unlikely to be helpful: - if it timed out, chances are the short delay before reattempting won't give the remote enough time to recover from its outage and a longer delay makes the job pointless as users likely scrolled further already. (Likely this is already be the case after the first 20s timeout) - if the remote data is so borked we couldn't even parse it far enough for an "invalid metadata" error, chances are it will remain borked upon reattempt |
||
|---|---|---|
| .. | ||
| benchmark.exs | ||
| config.exs | ||
| custom_emoji.txt | ||
| description.exs | ||
| dev.exs | ||
| docker.exs | ||
| prod.exs | ||
| test.exs | ||