-
-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to ignore hubcaps failures #474
Comments
You can use
We should make the retry interval configurable. It's currently making three attempts and waits 1, 2, and 4 seconds respectively between each retry. |
@DanySK did this fix your issue? |
Partly: it can skip 429 entirely, but retry count and timeout can't be set. |
True, we should make those configurable. I just keep forgetting to do it. 😅 |
The retry count is already configurable through |
|
A proper solution would be #36, with which we track the individual state of every website. This way we avoid overloading the servers and can do proper rate-limiting by parsing the respective headers and storing them in the website state. |
I'm waiting for the option to hit docker hub, as soon as it does I'll try it out |
Hum... it should already be in.
I'm away from my computer so I can't verify. |
I am using |
Yes, |
Guess we can close this. |
Hi,
I'm using lychee to check link integrity for a whole website.
Does the tool check the same link multiple times? Despite providing a valid token, I get many:
That I would not expect.
Is there a way to tell lychee to ignore these errors?
Something like
--ignore-error=429
would be great.Alternatively or in addition, would it be possible to wait and retry after a 429?
Something like
--wait-after-cap=60
to retry links after a minute if the cap has been reached.The text was updated successfully, but these errors were encountered: