You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that sometimes, URLs are not retried properly. The most recent example is job 172fw8g4egszevx4i56uu06cm. One of about 1700 such URLs on that job:
This URL was only attempted once and obviously not retrieved correctly. Further, no ignores matching this URL were present. So it should've been retried, yet it wasn't. I've seen another example of this in the past couple months but can't find it anymore.
I haven't looked into this in detail yet. One thing I noticed (but may be entirely irrelevant) is that all affected URLs on that job, per my crude check with a couple samples from wpull2-log-extract-errors in my little-things, are on https://usc.gov.mm/. Note that the job was started on HTTP, and the HTTPS server on that domain is actually broken.
The text was updated successfully, but these errors were encountered:
I've noticed that sometimes, URLs are not retried properly. The most recent example is job 172fw8g4egszevx4i56uu06cm. One of about 1700 such URLs on that job:
This URL was only attempted once and obviously not retrieved correctly. Further, no ignores matching this URL were present. So it should've been retried, yet it wasn't. I've seen another example of this in the past couple months but can't find it anymore.
I haven't looked into this in detail yet. One thing I noticed (but may be entirely irrelevant) is that all affected URLs on that job, per my crude check with a couple samples from
wpull2-log-extract-errors
in my little-things, are on https://usc.gov.mm/. Note that the job was started on HTTP, and the HTTPS server on that domain is actually broken.The text was updated successfully, but these errors were encountered: