Hold umami's check to the share route's own 404, so an unknown route cannot pass it (hq issue 145, review 262)
mesh/delivery-group group fix/145-a-consumer-is-held-under-its-provider delivering: 0 of 2 delivered
mesh/merge-gate head 2bb5d344f6f1 merged into trunk af5cf53a3450 — pass: builds gitea, mesh-knowledge, n8n, nextcloud, umami → ace, novox; no bus step; eve…
mesh/repo-check head 2bb5d344f6f1 merged into trunk af5cf53a3450 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/delivery held for a person: its group fix/145-a-consumer-is-held-under-its-provider's composed check did not pass for the heads that merged; a perso…

Any route umami does not serve answers 404 too, as an HTML page. The
share route answers JSON with code not-found only after the database
was asked; with the database down it answers 500.
This commit is contained in:
jochen
2026-10-14 07:07:11 +02:00
parent b62bb15839
commit 2bb5d344f6
+1
View File
@@ -94,6 +94,7 @@
"endpoint": "web", "endpoint": "web",
"path": "/api/share/mesh-health", "path": "/api/share/mesh-health",
"status": 404, "status": 404,
"body": "\"code\":\"not-found\"",
"timeout": "10s", "timeout": "10s",
"needs": "postgres-database" "needs": "postgres-database"
}, },