Seems like he’s been pushed into using LLMs as a way to cope with the deluge of LLM-generated security reports.

  • Buddahriffic@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    17 hours ago

    Any specific issues though? Yeah, it’s a large change and I’d be more surprised if it didn’t have issues, but are there any specific issues with the updates that have been found so far?

      • fruitcantfly@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        10 hours ago

        Yes, there’s been several regressions that would’ve been caught by the original tests, but missed by the new vibe-coded tests.

        That is directly contradicted by what the developer of rsync wrote in the linked article:

        yes, there were regressions in some use cases of rsync in the 3.4.3 release. … None of those cases were covered by the existing rsync test suite or by all the manual testing I did (yes, I use rsync, I don’t just develop it).

        It’s possible that somebody in the issue you linked to pointed to a test that would have caught one of the regressions, but I was not able to find it in the 327 comment mess. A direct link would be appreciated, if that is the case.

        But I doubt that you will find such a comment. Because I tried running the 3.4.1 test-suite with the 3.4.3 binary, and all tests passed

        • ooterness@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          5 hours ago

          Seems I was mistaken. My previous statement was based on what others have said, but I haven’t actually run the tests myself. In any case, I have learned not to rely on statements made by the accused in this type of dispute.