Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

Post reply on HN
Print view View original

121–130 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#121

Post by ncruces »

shimman wrote: post #11
scared_together wrote: post #6

Earlier quoted context omitted.

When I look at the commits themselves, most of the ones generated by Claude are testsuite changes, or at least labelled as such. https://github.com/RsyncProject/rsync/commits/master/

Is that suppose to make this better? IME the most valuable tests are those that test specific regressions. It's the scaffolding we build for ourselves to enable feature development. Remove that scaffolding and you get accidents. Pray to your god of choice these accidents don't cause harm or loss of life. It should really be considered negligence at this point. Some of this software is extremely valuable, it's how we…

Taken at face value, most commit descriptions mention adding - not skipping - tests and assertions.

So basically, we're all in our high horses, not reviewing code, scalding the unpaid maintainer for … not reviewing code.

Time for - whoever actually cares - to do better.

Re: Please Do Not Vibe Fuck Up This Software

#123

Post by reliablereason »

eloisant wrote: post #96

Is there any evidence this was broken by AI? I feel like these day any time users find an issue in software they blame it on "vibe coding". But software had bugs before AI.

The issue is apparently this commit (someone did a git bisect):

https://github.com/RsyncProject/rsync/commit/859d44fa4f14207...

Which is a fix to the security issue CVE-2026-29518: https://nvd.nist.gov/vuln/detail/CVE-2026-29518

A CVE reported by VulnCheck which is a company that uses AI to find software vulnerabilitys.

I would honestly blame this on bad test coverage.

If you look at most of the commits where Claude is "co-author" you see that 80% of are just adding new tests. Which is exactly what would be needed if low test coverage was the issue.

I have done the exact same thing long before AI was a thing. You are rushed to "FIX" some security issue that someone reported. It is a scenario where you are working in code that you did not write or you wrote it so long ago that you cant remember. You try your best to just fix the security issue but you perturb something else while doing it.

Re: Please Do Not Vibe Fuck Up This Software

#124

Post by bakugo »

michaelmrose wrote: post #98
nottorp wrote: post #42

Earlier quoted context omitted.

> is almost completely context free on what the drama is beyond "Claude" As soon as it happened their rsync based backup system that was working before started to fail. It says right there.

The source code is all right there. An actual analysis would involve a complete description of what you were doing including code they are running proving that what you were doing is reasonable and correct and expected to work. An explanation of what actually happened and ideally the exact commit where it stopped working. A users bald assertion that something is "broken" with no details should be regarded with suspic…

Why should a random user bother analyzing the code when the "developer" didn't bother doing the same before committing huge chunks of AI generated code?

The effort put into the issue was roughly the same as was put into the release that caused the issue to be made. Fair is fair.

Re: Please Do Not Vibe Fuck Up This Software

#125

Post by consp »

thevinter wrote: post #116

This whole brigading is bizzarre and some people are behaving like irrational animals. I potentially understand the motivations that might bring one to want to "win" this battle but this really isn't it - it just makes you sound like a fanatic. It takes 5 minutes to search for "regression" on the issue page and go through the 17 results. There are potentially even more on the tracker used prior to github. I think thi…

> I think this behavior is very silly and people are just trying to justify their hate to AI by latching onto every possible thing

It's not silly to have issues with something. People act on their issues. Possibly not the issue underlying the commit at hand here but something else, and act on it which makes it something to consider. My guess is people are tired of the "AI is the greatest thing since [cultural reference]" being forced down their throat and grasp at every straw to combat it, which is a sane response in my opinion and should be taken into account.

Re: Please Do Not Vibe Fuck Up This Software

#126

Post by izacus »

mattbee wrote: post #82
baliex wrote: post #43

Earlier quoted context omitted.

I 100% agree with the "please don't fuck up this stable & reliable workhorse" sentiment. I haven't read this in detail but "Six CVEs are fixed in this release. All six are assigned by VulnCheck as CNA. Affected versions are 3.4.2 and earlier in every case." seems like a pretty solid answer to the "why". https://download.samba.org/pub/rsync/NEWS#3.4.3

But there's been security fixes in most releases of rsync! Even then, why would a security fix be some kind of strike against AI? We've all seen LLMs being used to tease out the most serious and obscure bugs in C codebases. I'd expect to see a lot of security fixes for an ancient, well-used codebase when an LLM analyses it. Where is the slop commit here? And why is that commit evidence that tridge has lost his mind t…

The part you're missing is that those "fixes" broke a lot of existing functionality.

Re: Please Do Not Vibe Fuck Up This Software

#127

Post by brabel »

Hendrikto wrote: post #55
vsgherzi wrote: post #31

I also hate the ai slop but on the flip slide this maintainer has been asking for help for years and dosent receive much in the discord. I also want quality code but don’t jump to demonize a volunteer especially when not many have jumped in to help

Did he ask for help in churning all the code for no reason? Rsync was complete software. It does not need features, it needs stability and merely maintenance. If the author used AI for small, well-reviewed maintenance changes, that would be okay. But instead he is making large and sweeping changes that are entirely uncalled for and cause breakage. If the maintainer is overworked, that is even more reason not to do th…

What the hell why are you thinking you decide anything?? The man has his project and can do whatever he wants with it. Read the license.

Re: Please Do Not Vibe Fuck Up This Software

#128

Post by izacus »

Quarrel wrote: post #59
koehler wrote: post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

wtf is this comment section? The author of these commits were tridge & claude. What does tridge have to do to convince the open source community that he might be a legit programmer & have a clue? Samba? Whats that? Rsync? Never heard of it. Tivo? No clue (maybe more Australian context here than others, but still). Even the comments on the github issue, are totally devoid of the context that this is a very senior open…

> Is there any evidence that the bug rate on rsync is any worse than it used to be? or just a screenshot from mastadon?

There's plenty of evidence that rsync 3.4.3 has broken a bunch of features like incremental copies, yes.

Which is why your post is a great proof of how AI derangement can make previously great engineers output broken dangerous slop.

Re: Please Do Not Vibe Fuck Up This Software

#129

Post by joshka »

Quarrel wrote: post #59
koehler wrote: post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

wtf is this comment section? The author of these commits were tridge & claude. What does tridge have to do to convince the open source community that he might be a legit programmer & have a clue? Samba? Whats that? Rsync? Never heard of it. Tivo? No clue (maybe more Australian context here than others, but still). Even the comments on the github issue, are totally devoid of the context that this is a very senior open…

[flagged]

Re: Please Do Not Vibe Fuck Up This Software

#130

Post by KolmogorovComp »

Seem to me some people have forgotten about FOSS projects

> 15. Disclaimer of Warranty.

> THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

Post reply on HN