Skip to content

Research log

Two API facts the code was wrong about, both found by fetching

  • The change payload carries no file content. o=ALL_FILES returns only metadata (lines_deleted, old_sha, size_delta). Hunks now come from Gerrit's own diff endpoint, which also keeps hunk boundaries identical to what the reviewer saw.
  • after: filters on last update, not creation. after:2024-10-01 before:2024-10-03 returned a change created 2024-08-26. The post-cutoff contamination argument rests on creation date, so created_on_or_after enforces it client-side.
  • in Corpus
  • 1 min read

First real fetch: October 2024 OpenStack
changes returned by the query 2,350 in 24 pages, 13s
dropped as created before the cutoff 672 (29%)
kept 1,678
snapshot size 503 KB gzipped NDJSON
owners reduced to a pseudonym only 1,678 / 1,678

The 2,350 matches the figure the direction spec quotes for October 2024, so the query is selecting what it intended. The 29% is the after: bug measured rather than argued: without the client-side created_on_or_after filter, 672 changes created before the base model's release date would have entered the corpus, and the contamination argument would have been false while appearing to hold.

Repo split from phalanx-fl

The corpus and measurement code was built inside phalanx-fl and moved here. It had grown to 80% of that repo's test suite while importing exactly one function from it, in a repo whose stated purpose is a Flower testbed.