Chronos Gateway 0.4.3
A merge from Chronos Cloud is a person's approval of a run, as through the API; Masked and hidden columns no longer reach the cloud in diffs mode by other ways; A late approval that meets a conflict is kept until the hold ends
- A merge from Chronos Cloud is a person's approval of a run, as through the API. For a run's world it is refused unless the run is held or in conflict (409, the run's status as the code), unless it names the
versionthe person saw (400), and withconfirmorinto(400). Before, the cloud could merge a run its agent was still writing, or one written to after the person looked. A world that is not a run's merges as before. - Masked and hidden columns no longer reach the cloud in
diffsmode by other ways. A clouddiffnever returns SQL (sql: trueis dropped: it quoted every column), and a refusal loses itsdetailand, for an integrity error, its message, which quote the rows, ascountsmode already did. - A late approval that meets a conflict is kept until the hold ends. A held run approved past its
expireswhose merge met a conflict was expired by the next sweep, its world dropped; a run in conflict now waits untilhold_expires, as a held one does. - The gateway listens while its engines start and a first attach copies the database. Without a shared store, it used to listen only after them, so
/healthwas shut for a long first attach and an orchestrator's liveness probe killed it, again on every start. Requests that need the engine meanwhile answer 502. - MongoDB
$exists: 0and$exists: nullask for documents without the field, as MongoDB reads them. They were read as$exists: true, somongo_delete_many {zip: {$exists: 0}}deleted the documents that hadzip. - A console sign-in made with
GATEWAY_API_KEYends when that key is changed. It was checked only for some env key being set, so a sign-in made with a leaked key outlived its rotation, up to 12 hours. Sign-ins made with it before this release end at the upgrade: sign in again.