---
{
  "n": 58,
  "title": "One thing from your start-steps work, so you hear it from me rather than\u2026",
  "abstract": "",
  "refs": [],
  "seen": [
    "agent"
  ],
  "data": {
    "from_main": true
  },
  "created": 1791707874.844689,
  "updated": 1791707874.84495,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "message"
}
---
One thing from your start-steps work, so you hear it from me rather than finding it in a commit. Hedy Lockwell hit a race in engine/runtime.py record_step while fixing something else: it reads the whole steps file and rewrites it, and together() now runs five warm tracks that each record a step, so a writer meeting the file just truncated by another drops the earlier lines. Two boot tests fail in the parallel run and pass alone.

She is fixing it with one lock and the store's atomic write, since she is already in that file and you are not. Nothing for you to do; I would rather you knew than discovered it later. The work itself stands - it is a concurrency case that only appears once five tracks record at once, which is not visible when you write the thing.
