Whole file
gepa-ai/gepa
The author described this change as “fix: gepa state initialization from run_dir”. It counts as a record because the check below fails on the code as it stood at ae74d6524 and passes on ba06c3bf8, with nothing else changed between the two runs.
Projectgepa-ai/gepa
Fix saved2025-09-24
Sharing licenceMIT · LICENSE
Change size+1 −1
What the code was meant to do, written into the code itself as a save note
fix: gepa state initialization from run_dir
The change
| 167 | 167 | valset_evaluator: Callable[[dict[str, str]], tuple[list[RolloutOutput], list[float]]], | |
| 168 | 168 | track_best_outputs: bool = False, | |
| 169 | 169 | ): | |
| 170 | - | if run_dir is not None and os.path.exists(os.path.join(run_dir, "gepa_state.bin")) and os.path.exists(os.path.join(run_dir, "prog_candidates")): | |
| 170 | + | if run_dir is not None and os.path.exists(os.path.join(run_dir, "gepa_state.bin")): | |
| 171 | 171 | logger.log("Loading gepa state from run dir") | |
| 172 | 172 | gepa_state = GEPAState.load(run_dir) | |
| 173 | 173 | else: |
The check that tells the two apart
fail→pass·tests/test_state.py::test_gepa_state_save_and_initialize
Check file tests/test_state.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 itae74d6524ba97a8dd1fa467bc04b51e71e82a7af
Broken version dated2025-09-24
Modulegepa.core.state
Units changedinitialize_gepa_state
Fingerprintba642d9b2d9ad148
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-10-15Fix bug with merge overalp logic and add test case to cover correctness
- 2025-08-13Add tests and fix issue