Repository navigation
docs(postmortem): 0007 - deployed into a scored run, and dropped a field no test watched - #149
Merged
Merged
Conversation
…eld no test watched
Two failures reached main and the live endpoint on 2026-11-01 and neither was caught
by anything that existed. The release tag is not their home: a tag answers 'what is
this version', a post-mortem answers 'why did this get through'.
Failure class: rule not on the action path. The 'no deployment between the start and
the end of a scored run' rule lived in 0006 and was not consulted at deploy time,
because the deploy is a shell command and the run's state is a browser tab. The second
case is the same shape: a refactor removed persistence.inline_bytes and the suite stayed
green because no test asserted the field; a linter reported the correct symptom of the
wrong class ('unused variable').
Guardrails now on the artefact rather than in prose: the built edgeone.json must not
contain schedules, and every search page must carry a numeric inline_bytes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc owner:
docs/postmortem/0007-deployed-into-a-run-and-dropped-a-field.{md,zh-CN.md,terms.yaml}(new) and the index rows indocs/postmortem/README{,.zh-CN}.md.Two failures reached
mainand the live endpoint on 2026-11-01, and neither was caught by anything that existed:schedulesinedgeone.json→ 404 on/health,/add,/search). The rule against it already existed in postmortem 0006 and was not consulted at deploy time.persistence.inline_bytesfrom every search response.verifystayed green because no test asserted the field; a linter reported the correct symptom of the wrong class ("unused variable").Failure class: rule not on the action path.
This record also exists because I first wrote the self-criticism into the
v1.4tag message, which is the wrong owner: a tag answers "what is this version", a post-mortem answers "why did this get through". The tag was rewritten to describe the release only.Guardrails land on artefacts rather than prose: the built
edgeone.jsonmust not containschedules(test), and every search page must carry a numericinline_bytes(test).