Whole file
gepa-ai/gepa
The author described this change as “Fix bug with merge overalp logic and add test case to cover correctness”. It counts as a record because the check below fails on the code as it stood at 0189a8ed0 and passes on 040ca675c, with nothing else changed between the two runs.
Projectgepa-ai/gepa
Fix saved2025-10-15
Sharing licenceMIT · LICENSE
Change size+1 −1
What the code was meant to do, written into the code itself as a save note
Fix bug with merge overalp logic and add test case to cover correctness
The change
| 264 | 264 | if self.val_overlap_floor <= 0: | |
| 265 | 265 | return True | |
| 266 | 266 | common_ids = set(state.prog_candidate_val_subscores[id1].keys()) & set( | |
| 267 | - | state.prog_candidate_val_subscores[id1].keys() | |
| 267 | + | state.prog_candidate_val_subscores[id2].keys() | |
| 268 | 268 | ) | |
| 269 | 269 | return len(common_ids) >= self.val_overlap_floor | |
| 270 | 270 |
The check that tells the two apart
fail→pass·tests/proposer/test_merge.py::test_merge_proposer_skips_pairs_below_overlap_floor
Check file tests/proposer/test_merge.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.
Origin and history
The code before it0189a8ed0a46dc4fe4e256eddc8f3b8a612a4ac4
Broken version dated2025-10-14
Modulegepa.proposer.merge
Units changedMergeProposer
Fingerprint9d2c99be9f1a7801
Checked2026-08-18 by goldset/0.1
Every field above is generated by our program. None of it is written by hand.
Other bugs found in gepa-ai/gepa
- 2026-08-11_from_legacy_config
- 2025-10-23EpochShuffledBatchSampler
- 2025-09-24fix: gepa state initialization from run_dir
- 2025-08-13Add tests and fix issue