According to Microsoft, users who have installed the KB5095051 update might encounter a strange Recycle Bin bug that replaces the names of deleted files with internal Recycle...
Clickbait and misleading. Nothing “broke”. The recycling bin works just fine, the name of the file in the confirm delete popup is just displayed wrong.
It isn’t the details or severity of the break that matters.
It’s that the quality control process is SUPPOSED to catch that, and whatever sorry excuse for a process they’re using now ALLOWED a break that was obvious, visible, and repeatable, inside a critical, core function of the operating system, to make it to the end users, something that should trigger as an immediate, flashing warning light. That means the entire quality control process at the very least is SEVERELY compromised and unreliable, and there could very easily be MUCH more severe vulnerabilities and bugs hiding underneath that AREN’T immediately visible. To anyone who has done any professional development for non-disposable code bases, this isn’t a whisper of a problem - it’s an air horn.
I have seen things mislabeled in Linux in the past, I’ve also seen minor bugs in Linux. It’s not broken if the software still works fine. Bugs happen with or without AI.
Linux doesn’t charge hundreds of dollars per license to fund the development, rake in billions in profit, and then funnel that money into stock dividends instead of a proper quality assurance team.
Clickbait and misleading. Nothing “broke”. The recycling bin works just fine, the name of the file in the confirm delete popup is just displayed wrong.
It isn’t the details or severity of the break that matters.
It’s that the quality control process is SUPPOSED to catch that, and whatever sorry excuse for a process they’re using now ALLOWED a break that was obvious, visible, and repeatable, inside a critical, core function of the operating system, to make it to the end users, something that should trigger as an immediate, flashing warning light. That means the entire quality control process at the very least is SEVERELY compromised and unreliable, and there could very easily be MUCH more severe vulnerabilities and bugs hiding underneath that AREN’T immediately visible. To anyone who has done any professional development for non-disposable code bases, this isn’t a whisper of a problem - it’s an air horn.
AI found the exploits, and they clearly used AI to fix the exploits… That about as far as the QC conversation went
Lol, yeah that’s definitely broken
So, nothing broke, except the thing that broke. Gotcha.
That sounds kinda broken…
I have seen things mislabeled in Linux in the past, I’ve also seen minor bugs in Linux. It’s not broken if the software still works fine. Bugs happen with or without AI.
Linux doesn’t charge hundreds of dollars per license to fund the development, rake in billions in profit, and then funnel that money into stock dividends instead of a proper quality assurance team.
Depends on the distro.
Hundreds of dollars per license, and they still run ads in the os…
Linux is zero dollars and shows zero ads…
Ubuntu has ads
So where is it pulling that data from?
What other file identifying functions are broken in a similar manner?
Sounds like Copilot code.