Release · S322–S322
Two of our own measurements were watching the wrong thing
This site keeps a written record of which version of itself is running, and it checks that record against what is actually being served. That check looked only at fields whose NAME ended in a particular way. Two other fields in the same file held the same kind of value, and both were out of date — naming a version from two releases earlier — while the check reported everything as agreeing. One of them sat next to a note saying it had been read directly from the live site, which made it a claim about an observation that was never made. The check now looks at the VALUE rather than the name of the field. Anything in that record that looks like a version is compared against what is really running, and anything unrecognised is treated as a problem rather than ignored. A version mentioned inside a sentence is still just a sentence, not a claim, and that distinction falls out of how the check works rather than from a list someone has to maintain. The second measurement concerns storage. This site holds its data in a single row with a hard size limit, and it keeps a reserve for the parts it cannot measure precisely. The measured amount has been over that reserve for a while. That is deliberately visible and is why the health page reports itself as not ready; the site itself has been serving normally throughout. What was missing is that nothing recorded whether the gap was GROWING. It was. It grew by about 54 kilobytes in twelve days, and no part of the system had written that down — the running total that was being tracked turned out to be a different figure from the one the warning is based on. The site now records the right figure over time and will say whether the gap is widening, narrowing, holding steady, or moving in both directions. Until it has watched for long enough it says so plainly instead of guessing. What this does not do: it does not make the storage limit further away, and it does not change what is stored. Participant export and deletion remain unavailable for the reasons given in earlier notes.