Issue Monster: eliminate false-positive 429 rate-limit detection#41471
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
Fix over-aggressive 429 detection in Issue Monster
Issue Monster: eliminate false-positive 429 rate-limit detection
Jun 25, 2026
Copilot created this pull request from a session on behalf of
pelikhan
June 25, 2026 14:25
View session
pelikhan
approved these changes
Jun 25, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR tightens Issue Monster’s rate-limit detection so it no longer treats arbitrary “429” substrings (e.g., PR numbers like #41429) as a real HTTP 429/rate-limit signal, preventing premature skipping of issue assignment.
Changes:
- Update
issue-monstercomment-scanning regex to require a standalone429token (\b429\b). - Regenerate
issue-monster.lock.ymlto reflect the updated workflow source. - Regenerate Copilot smoke lock workflows, including changing compiled strict-mode reporting to
false.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/smoke-copilot.lock.yml |
Regenerated lock file; changes compiled strict-mode flag to false. |
.github/workflows/smoke-copilot-aoai-entra.lock.yml |
Regenerated lock file; changes compiled strict-mode flag to false. |
.github/workflows/issue-monster.md |
Tightens rate-limit regex to avoid false-positive 429 substring matches. |
.github/workflows/issue-monster.lock.yml |
Regenerated lock file to incorporate the updated Issue Monster regex. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 4/4 changed files
- Comments generated: 2
| GH_AW_INFO_FIREWALL_TYPE: "squid" | ||
| GH_AW_INFO_FRONTMATTER_EMOJI: "🧪" | ||
| GH_AW_COMPILED_STRICT: "true" | ||
| GH_AW_COMPILED_STRICT: "false" |
| GH_AW_INFO_FIREWALL_TYPE: "squid" | ||
| GH_AW_INFO_FRONTMATTER_EMOJI: "🧪" | ||
| GH_AW_COMPILED_STRICT: "true" | ||
| GH_AW_COMPILED_STRICT: "false" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Monster was treating unrelated text as a 429 signal and prematurely skipping issue assignment. In practice, PR metadata like
#41429matched the old pattern and triggered the rate-limit guard incorrectly.Problem scope
issue-monstercomment scanning was too broad.429could be interpreted as a real HTTP 429 indicator.Change
429token instead of arbitrary substring matches.Behavioral impact
429,rate limit,secondary rate limit,abuse detection,too many requests).