7 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	41cdd03208	Keep serving the consumers postgres's grant file gives on its moved path (issue 937) ... Only a moved consumer's plan names postgres, so on the moved path every consumer still given by the controller's grant file was counted unasked and offered for retirement (ace 5 of 5, novox 7 of 9), and could have been retired unasked where the bound allowed. The moved path now reads MESH_RECEIVES again: its logins are asked, the ones no plan names are made and checked by the harness's grant pass until R1 (issue 682), and an unreadable grant file retires nothing (issue 241). The harness's grant pass becomes apply, identically in keycloak's copy.	2026-10-16 16:25:52 +00:00
jochen	2c15074a0b	Retire only once the same answer has held ten minutes as well as five passes ... Five passes are twenty-five seconds, shorter than a controller restart, a store reconnecting or a file half written; the operator asked for both (hq ADR 0230).	2026-10-06 14:28:21 +02:00
jochen	e68ef88333	Retire a consumer the mesh stops asking for, and delete only on a person's word (hq ADR 0230) ... The hourly release of ADR 0229's brake still ended in the mesh acting alone on a mistake. A consumer now stays active until the same unasked set holds for five passes, waits for a person past three or half of those held, is disabled and marked rather than withdrawn, comes back as it was when asked again, and is deleted only through the provider's delete tool. The backend keeps the mark, so a restart forgets nothing and finds what was withdrawn before.	2026-10-06 13:54:10 +02:00
jochen	4238dd8616	Name the SDK harness the Go loop follows: 0.1.11, with the withdrawal brake	2026-10-06 12:29:21 +02:00
jochen	2c151e7c21	Brake a withdrawal larger than its bound (hq to-be 45 Phase 2, ADR 0227 rule 4) ... Issue 241 withdrew seven consumers in one pass on one misread file; its fix refuses a file it cannot read, and a file read whole that names nobody still withdraws everybody. A pass that would withdraw more than one consumer at once, or more than half of those it holds, now withdraws nothing: each consumer it kept is announced provisioner.failing with the class withdrawal-braked, so the controller raises it as a condition and the operator is told, and one is let go each hour while the mesh goes on not asking for them. A consumer asked for again is kept and said recovered. Postgres and keycloak carry the harness identically.	2026-10-06 12:29:21 +02:00
jochen	6f1e2f5a0d	postgres: announce a consumer failed for minutes, and its recovery ... A provider failed every consumer for a day and said so only in its journal (hq issue 179). The provisioner loop now emits provisioner.failing after five minutes without a success — create, check or secret — and repeats it every fifteen; provisioner.recovered on the next success, on withdrawal, and on the first success after a restart, so the controller can name it in status (hq ADR 0224).	2026-10-06 00:13:42 +02:00
jochen	d8b4d20886	Port postgres to Go and install the extensions a consumer asks for ... letta crash-loops on 'type "vector" does not exist': pgvector is not a trusted extension, so only the provider's superuser can create it, and the provisioner never did. A contribution may now name extensions; the provider creates each (IF NOT EXISTS, available ones only) in the consumer's database on every pass. Go per the standing rule for a TypeScript module that changes. letta asks for vector.	2026-10-05 23:29:55 +02:00