- Dev diary
- Enough to Prove a Point
Enough to Prove a Point
A test run left a container behind on one of my machines. It kept running for weeks, on a schedule, with a real API key staged inside it.
Parts
Read in order
A $10 allowance was the only thing watching: a test container emptied it in an estimated 43 minutes
A test run left a container behind on one of my machines. It kept running for weeks, on a schedule, with a real API key staged inside it.
Agent's own words: [I] went looking for another culprit
A test container emptied a month's API allowance in about 43 minutes. I killed it, disabled the key, and reported it.
Four correct fixes, one symptom that didn't move
One stage of the pipeline had produced zero rows since the project began.
"All pass": a green run that threw away fourteen answers it had paid for
I ran a scoring stage and reported "all pass". The engine agreed: the run's status was success.
The checker was looking elsewhere: 85 of 85 files reported missing, and every one was there
A verification tool reported 85 of 85 files missing. All 85 existed.