Login
You're viewing the discuss.systems public feed.
  • Oct 5, 2026, 1:13 PM

    @wfk

    There's some FUD here if I read the actual history right.

    3.4.3 had no AI contributed code (in theory see below). It did, however, have some regressions that were *found* by humans using AI.

    In response, Andrew Tridgell used AI assistance to rewrite the test suite, moving it from shell to python and making improvements, to cover the regressions - and his commits acknowledge this. The assertion is the AI was only used for the test suite, not for the actual rsync code. It seems unlikely to me he'd acknowledge it in the test suite but hide it in the actual code.

    3.4.4 is the result that should fix those regressions, although 3.5 is also coming down the pipe with "security fixes", whatever that might be.

    There's no indication that any AI-assisted coding is in the actual binary. Just good old human mistakes. Unless of course people lie about their AI use, or more charitably simply omit that data from their commits. There are no hard guarantees about code provenance, but then there never were, in any project. There's also no AI policy for that project I am aware of.

    Open source is open for reasons. One of those is you have no real guarantees of fitness - so here's the code, audit it yourself. I think we sometimes forget that and take the hard work of others for granted.

    💬 2🔄 1⭐ 7

Replies

  • Oct 5, 2026, 1:22 PM

    @tbortels ah, I'll need to dig a bit deeper to see what the real sequence of events was. My understanding was that the instabilities started after the introduction of Claude generated code. If things had already gone south before that, I missed that bit.
    Still feeling decidedly uncomfortable trusting Claude generated code is such a critical bit of software.

    💬 1🔄 0⭐ 1
  • Oct 5, 2026, 2:54 PM

    @wfk

    I tend to agree, but pragmatically - it's open source. Your alternatives also have no guarantees of provenance or quality. And closed source is worse - at least this way we could, in theory, audit.

    And if I have the time line right - big If, but hey - the first introduction of AI was a flood of AI generated external bug reports, which is what prompted the revamp of the test suite. The alternatives were maybe to ignore the reports, or manually update the tests?

    And I'd repeat: no AI in the mainline code *that we know of*. Guarantees there will be hard to come by. The price we pay for free code is that people do things we may not approve of or know about.

    I personally backrev on purpose. The world is my beta tester. :-)

    💬 0🔄 0⭐ 1
  • Oct 5, 2026, 3:07 PM

    @tbortels

    so I checked the git log.

    Claude contributions startled showing up before 3.4.2.

    The version that tripped me up was 3.4.3.

    So, no FUD there on my part.
    The change that caused me trouble was right after Claude contributions appeared in the log. That doesn't mean necessarily that the bad code was actually written by Claude, but it does mean that it happened right after a flood of Claude changes went into the repo.

    💬 0🔄 0⭐ 6