From 17b64270b096f46febe9dde753615a40ca242288 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 9 Oct 2026 14:22:17 +0200 Subject: [PATCH] Issue 348: the manifest test takes either binding until the catalogue merges --- .../01-diagnosis.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md b/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md index 00a9e8ce..91f3aaa4 100644 --- a/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md +++ b/04-ISSUES/348-a-resolver-that-stopped-answering-ran-on-unnoticed-and-builds-sent-after-it-were-blamed/01-diagnosis.md @@ -175,4 +175,5 @@ registry, is the operator's decision. A replay in mesh-lab's register is still owed before this core issue resolves (ADR 0237). The controller's own test of the resolver's manifest (`TestTheResolverForwardsToFixedUpstreamsAndNeverReadsResolvConf`) -now asks for `bind-interfaces` and refuses `bind-dynamic`, so the two pull requests land together. +reads the catalogue beside it, so for now it takes either binding; once the catalogue's main binds once, +it should refuse `bind-dynamic` (a follow-up in the controller).