- Notifications
You must be signed in to change notification settings - Fork1.1k
fix: throttle prebuild notifications#18483
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
92b5e63 to272c338Compareae7135c tobd04330Comparebd04330 to362911eComparedannykopping commentedJun 24, 2025
I'mreally not a fan of this approach. It feels like we're just digging ourselves a deeper hole of technical debt instead of addressing the core issue. We should move towards a daily or weekly summary email, like we have done for other build failures, and put logging and observability in place for operators to notice when problems occur with lower latency & greater resolution. |
Uh oh!
There was an error while loading.Please reload this page.
Closescoder/internal#674
Description:
Note:
It's done per template:
We can have multiple broken templates - in this case Template Admins will get one notification per template per 7 days.
I think it shouldn't be more than few notifications per week.
If it's still too noisy - we can consider making cooldowns global instead of template-specific. It should be enough to remove
template_idfield.