Skip to content
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

chore: have lock-threads fail silently #426

Merged
merged 1 commit into from
Jul 4, 2024
Merged

Conversation

xiehan
Copy link
Contributor

@xiehan xiehan commented Jul 4, 2024

There's really no reason to have our monitoring dashboard color red when this workflow fails, which happens pretty regularly due to rate-limiting issues that are hard to avoid.

Note that this is not a totally ideal solution because now we won't know if the workflow starts failing 100% of the time for any reason, but given that I don't think that's super likely and the status quo is annoying, I consider that a small price to pay.

@xiehan xiehan requested a review from a team as a code owner July 4, 2024 11:53
@xiehan xiehan requested review from ansgarm and DanielMSchmidt and removed request for a team July 4, 2024 11:53
@team-tf-cdk team-tf-cdk enabled auto-merge (squash) July 4, 2024 11:57
@team-tf-cdk team-tf-cdk merged commit 471b018 into main Jul 4, 2024
11 checks passed
@team-tf-cdk team-tf-cdk deleted the lock-threads-failures branch July 4, 2024 11:57
Copy link

I'm going to lock this pull request because it has been closed for at least 7 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue so we can investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants