Skip to content

fix: allow status code 429 for linkspector#7270

Merged
rfay merged 2 commits into
ddev:mainfrom
stasadev:20250506_stasadev_linkspector
May 6, 2025
Merged

fix: allow status code 429 for linkspector#7270
rfay merged 2 commits into
ddev:mainfrom
stasadev:20250506_stasadev_linkspector

Conversation

@stasadev

@stasadev stasadev commented May 6, 2025

Copy link
Copy Markdown
Member

The Issue

We get 429 from GitHub links for linkspector https://github.com/ddev/ddev/actions/runs/14861937842/attempts/2

It seems that GitHub changed some limits.

How This PR Solves The Issue

I noticed that we use GITHUB_TOKEN for actions (this is not the env itself, it's name for custom action variable) instead of github_token (IDE highlighted it for me)

Adds an exception for 429 status.

Manual Testing Instructions

Automated Testing Overview

Release/Deployment Notes

@stasadev stasadev requested a review from a team as a code owner May 6, 2025 15:11
@stasadev

stasadev commented May 6, 2025

Copy link
Copy Markdown
Member Author

@stasadev stasadev changed the title fix: use github_token for linkspector fix: allow status code 429 for linkspector May 6, 2025
@stasadev

stasadev commented May 6, 2025

Copy link
Copy Markdown
Member Author

Success with 429 status allowed in https://github.com/ddev-test/ddev/actions/runs/14863503281/job/41734319606

@rfay rfay left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we should do this for now.

@github-actions github-actions Bot added the bugfix label May 6, 2025
@rfay rfay merged commit 001530a into ddev:main May 6, 2025
@rfay rfay deleted the 20250506_stasadev_linkspector branch May 6, 2025 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants