So rsync rewriting all the tests puts the entire project in play. Now the entire protective surface has been sloshed through a layer of probability, so the loop must accelerate. Followup PRs add more carveouts with lengthy LLM justifications that sound perfectly plausible but amount to an erosion of the protective surface. We go from cumulative improvement to a random walk.
This is like a human cell goofing up its p53 genes and deciding that being cancer is good actually.
Has anyone run the set against the recently added coverage support? Do we know if there where test cases for the CVE behaviour before the faulty patches were added?
Has anyone run the set against the recently added coverage support? Do we know if there where test cases for the CVE behaviour before the faulty patches were added?