-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
accept 429 code not taken in account #1340
Comments
nvuillam
added a commit
to oxsecurity/megalinter
that referenced
this issue
Jan 7, 2024
nvuillam
added a commit
to oxsecurity/megalinter
that referenced
this issue
Jan 7, 2024
* [automation] Auto-update linters version, help and documentation * Fix lychee breaking change Upgrade lychee default configuration to handle [breaking change between 0.13.0 and 0.14.0](lycheeverse/lychee#1338) * Undowngrade revive * Fix lychee config until bug is solved lycheeverse/lychee#1340 * [MegaLinter] Apply linters fixes --------- Co-authored-by: nvuillam <[email protected]> Co-authored-by: nvuillam <[email protected]>
@Techassi, any ideas? |
Well, this seems rather interesting. I will look into it. |
This will be fixed by #1344. This is a one-line change that took me 1,5h to debug. My first thought was that our parsing is messed up (which it isn't), but the option set in the TOML config file never got used... :/ |
@Techassi great, thanks :) |
New release out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With 0.14.0
lychee.toml contains
But results considers as errors 429 status codes
The text was updated successfully, but these errors were encountered: