When Hermeto retries a failed HTTP download, no log output is produced. Both download paths retry on 500/502/503/504 status codes, but the retries are invisible in our logs even with --log-level=DEBUG. The underlying libraries do log retries, so it should be possible.
This could be improved from a UX perspective, since without retries being logged, a download that fails after multiple retry attempts looks like a single slow request that errored out. The ~10-second gap suggests retries occurred, but there's no attempt counts, no intermediate status codes, and no backoff durations show.
When Hermeto retries a failed HTTP download, no log output is produced. Both download paths retry on 500/502/503/504 status codes, but the retries are invisible in our logs even with
--log-level=DEBUG. The underlying libraries do log retries, so it should be possible.This could be improved from a UX perspective, since without retries being logged, a download that fails after multiple retry attempts looks like a single slow request that errored out. The ~10-second gap suggests retries occurred, but there's no attempt counts, no intermediate status codes, and no backoff durations show.