-
Notifications
You must be signed in to change notification settings - Fork 59
Duplicated comments for invalid configuration #2754
Copy link
Copy link
Closed
Labels
area/configRelated to the configurationRelated to the configurationarea/generalNot tied to a specific areaNot tied to a specific areaarea/user-experienceRelated to the UXRelated to the UXcomplexity/single-taskRegular task; should be done within daysRegular task; should be done within daysgain/lowDoesn't bring much value to usersDoesn't bring much value to usersimpact/highAffects a lot of usersAffects a lot of userskind/bugAn unexpected problem or behaviorAn unexpected problem or behavior
Metadata
Metadata
Assignees
Labels
area/configRelated to the configurationRelated to the configurationarea/generalNot tied to a specific areaNot tied to a specific areaarea/user-experienceRelated to the UXRelated to the UXcomplexity/single-taskRegular task; should be done within daysRegular task; should be done within daysgain/lowDoesn't bring much value to usersDoesn't bring much value to usersimpact/highAffects a lot of usersAffects a lot of userskind/bugAn unexpected problem or behaviorAn unexpected problem or behavior
What happened? What is the problem?
When an invalid configuration is handled, we report it for each retry (=>3 times), instead of just once. I believe we have a functionality for checking the duplicate comments (and I remembered we even used that) to avoid this.
What did you expect to happen?
No response
Example URL(s)
packit/hello-world#2880
Steps to reproduce
What is the impacted category (job)?
General
Workaround
Participation