погожим осіннім днем білочка в лісі назбирала букет айстр, бачить їжака
— ой їжачок, такий прекрасний день, ось тобі букет!
— мені? та ну, не нада мені воно…
— ой як це не нада, диви який гарний, бери вже!
їжак бере й
— воно-то канєшно дякую, але про всяк випадок іди-но ти нахуй
to fix chrome 157 window jumping all over the place when resized with opt + resize, restart it like this
open -a "Google Chrome" --args --disable-features=AsyncLiveResize
and add a comment to https://t.co/N1VwvNlirL
Got more details, it was NOT DNS, 100%. Also doesn't look like AI for those asking. And NOT "layoffs related" lol. But a seemingly complex set of networking problems caused by the legacy system
Mitigation was v complex: not just rollback network config changes, but eg registry key patches, rebooting specific racks, and dealing with the thundering herd problem via traffic routing
the root cause is still unclear even internally within MSFT (save for the incident team) and everyone awaits the postmortem eagerly. This will surely be a public one. I'll see if I can get details on top of the public postmortem from MSFT