Counterparts: Generate a random selection of commits that are not vulnerability-contributing commits

[andymeneely]

In this study, we want to examine the churn differences between vulnerability-contributing commits (VCCs) and non-VCCs.

We need to create some random samples of non-VCCs to compare against. This random sample needs from the files that had a VCC.

That is come up a random selection of X "counterparts" that were non-VCCs, but the same file. We will then compare those in terms of churn

Make whatever tables, Java, etc you need for this.

[andymeneely]

Ok - current work looks good thus far. I'm almost done integrating it into my master branch. Here's some stuff to finish before closing this one:

• Instead of parsing that CSV - use the CVEToGit table. It's already got that data parsed up (part of my recent changes)
• Let's re-structure the table a bit:
  • Ctrparts should be called "Counterpart",
  • One commit can have multiple counterparts, each on a new row. This means commit is no longer the primary key - make an autoincrement ID field for that. It'll be easier for me to aggregate this data with a GROUP BY than to parse it out each time.
  • Make the seed a property in httpdhistory.properties

Also, take a look at some of the stuff I did since your commits. In particular, check out my commit comments for 695736c5bf470b05cec93699efe48fffdc3b68d0. You did well on the conventions in general though.

Also, note that my changes in 061c5848caeb9d94c567fa9e6c00d1464aa5e9ec means you need to update your httpdhistory.properties

[andymeneely]

Also, the part about CVEToGit was re-enabled in d49ffc544c35e2301265473662593745ad5e7f61

[mok4ry]

In that case, and I was going back and forth on this the first time, I don't think it's worth it to have a Filepath column in the Counterparts table.

[andymeneely]

Agreed - we don't need it.

[mok4ry]

Modified code according to your comments. Changes are in my master branch.