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
### Errors in ./RELEASING.md
* [429] [https://github.com/open-telemetry/opentelemetry-go/commits/main](https://github.com/open-telemetry/opentelemetry-go/commits/main) | Failed: Network error: Too Many Requests
The two fixes here could be to get lycheeverse/lychee#1403 to move forward, so a links check that fails would still update the cache with URLs that succeeded, making retries only fetch the previously failing URLs, and fixing rate limit issues.
If we can't get that moving, we'll have to disable the links check temporarily, or have it consider 429s as success.
This considers 429s as a success, until we can get lychee to cache
success requests even if there's a failure.
This should only be a temporary measure. But ignoring one status code
seems better than entirely disabling the check.
Related: #6183.
Example: https://github.com/open-telemetry/opentelemetry-go-contrib/actions/runs/11151936706/job/30996462798?pr=6002
The text was updated successfully, but these errors were encountered: