5 Commits

Include renames

Author	SHA1	Message	Date
lead-57	deb2020bd4	Serve postgres's consumers the port its server is published on, not the container's 5432 (issue 957) ... On novox postgres is published 6852:5432; handed 5432, gitea and keycloak reached nothing once their files were filled from postgres's entry.	2026-10-16 21:56:15 +02:00
fix-cat-pas@novox	33759f8b57	Run postgres on the SDK's harness and moved path, dropping its copies (issue 849)	2026-10-16 19:35:22 +02:00
mesh-tools	6005c6001e	Ask the plans again when the moved path starts before its runtime answers (issue 943) ... postgres and keycloak start their moved path beside Serve, and a watch asked before Serve runs is refused by the runtime. Run returned on that refusal and main only logged it, so a start that lost the race left the provider answering nobody and retiring nothing until its next restart: postgres on novox at 16:52, 18:29 and 18:48, on ace at 16:22, which kept issue 937's retirement condition on novox from clearing. Run now asks again, the wait doubling from a second to a minute, until the runtime answers or its context ends.	2026-10-16 16:52:52 +00:00
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
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00