▲ | prmoustache 5 days ago | ||||||||||||||||||||||||||||||||||||||||||||||
Is "brownout" a common or standard term in the industry? First time I see it. | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | numpad0 5 days ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
Commonly used in microcontrollers to describe supply voltage dropping below threshold. It could cause RAM corruption, erratic behaviors of robots, overshoot in voltage regulators, battery fluid leaks etc., and so optional detection features are often made available to reset or stop the processor and notify the application on next boot. It's also used in utility power supplies to describe line voltage going below spec. It's considered a dangerous condition in that context too, as lots of non-smart equipment tend to run at higher amperage at lower voltage and/or fail to start/run and catch fire. 1: https://developerhelp.microchip.com/xwiki/bin/view/products/... | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | habitue 5 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
We did this at stripe when deprecating TLS 1.0, and called it a brown out (I don't know the origin of the term in software). You do it when you have a bunch of automated integrations with you and you have to break them. The lights arent on at the client: their dev teams are focused on other things, so you have to wake them up to a change that's happening (either by causing their alerting to go off, or their customers to complain because their site is broken) | |||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||
▲ | Beltran 5 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
Yes, another example of brownout at https://spring.io/blog/2022/12/14/notice-of-permissions-chan... It is probably the only way to warn users when you do not know the contact info. | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | 01HNNWZ0MV43FF 5 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
Yes I heard of GitHub doing it I think You intentionally break something just a little to force dependents to notice, before turning it off completely | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | usrme 5 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
There was actually a really terrible brown-out by Poetry (a Python dependency management and packaging tool) where they introduced sporadic failures to people's CI/CD systems: https://github.com/python-poetry/poetry/pull/6297 | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | aabhay 5 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
First heard about this when docker started rate limiting | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | miki123211 5 days ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
Yes. It refers to a situation where a system is deliberately designed to fail (usually for short periods of time), to still provide some level of service while alerting others that the system is soon to be turned off. | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | znpy 5 days ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||||||||
Yes. Going from green to red is called “browning out”. | |||||||||||||||||||||||||||||||||||||||||||||||
|