jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
The problem: a release prepares an answer for every setting at its default. For date fields (createdAt on Account, Domain, Tenant, OAuthClient and others, and a certificate's notValidBefore/notValidAfter), the "default" is the moment the object is built. So the question changed every run, about 11 answers were regenerated every release, and no live question ever matched them.
Some of that wording was wrong: one read "That date is in the future … check the server's clock".
The fix:prepared_questions skips a property whose default is an RFC 3339 timestamp. The next release's prepare drops those answers and asks nothing new about them. Live Explain this on a date field works as before and asks the model.
Checked:prepared_questions_are_well_formed now also asserts that x:Account.createdAt isn't prepared. The explanation tests pass.
Found while preparing 2026.9.28.5.
- **The problem:** a release prepares an answer for every setting at its default. For date fields (`createdAt` on Account, Domain, Tenant, OAuthClient and others, and a certificate's `notValidBefore`/`notValidAfter`), the "default" is the moment the object is built. So the question changed every run, about 11 answers were regenerated every release, and no live question ever matched them.
- **Some of that wording was wrong:** one read *"That date is in the future … check the server's clock"*.
- **The fix:** `prepared_questions` skips a property whose default is an RFC 3339 timestamp. The next release's prepare drops those answers and asks nothing new about them. Live *Explain this* on a date field works as before and asks the model.
**Checked:** `prepared_questions_are_well_formed` now also asserts that `x:Account.createdAt` isn't prepared. The explanation tests pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found while preparing 2026.9.28.5.
createdAton Account, Domain, Tenant, OAuthClient and others, and a certificate'snotValidBefore/notValidAfter), the "default" is the moment the object is built. So the question changed every run, about 11 answers were regenerated every release, and no live question ever matched them.prepared_questionsskips a property whose default is an RFC 3339 timestamp. The next release's prepare drops those answers and asks nothing new about them. Live Explain this on a date field works as before and asks the model.Checked:
prepared_questions_are_well_formednow also asserts thatx:Account.createdAtisn't prepared. The explanation tests pass.