From 6640c73015ebe3d9d751eabd8bce15a10b8787df Mon Sep 17 00:00:00 2001 From: Artur Shiriev Date: Thu, 24 Sep 2026 02:10:23 +0300 Subject: [PATCH] docs: record the drive-qualified bind as settled, not open ADR-0006 called it "what remains open" and cited #111, which had already closed as working as intended: the long form reaches the capability, and refusing the short spelling is the better tool on Linux, where it almost always means a drive that is not there. The conformance summary pointed readers at "the open limitation issues", of which there are now none. It names the two ADRs that hold the rulings instead. --- docs/adr/0006-docker-rejection-parity.md | 16 +++++++++++----- tests/conformance/conftest.py | 4 +++- 2 files changed, 14 insertions(+), 6 deletions(-) diff --git a/docs/adr/0006-docker-rejection-parity.md b/docs/adr/0006-docker-rejection-parity.md index 962a3d4..11d2fe7 100644 --- a/docs/adr/0006-docker-rejection-parity.md +++ b/docs/adr/0006-docker-rejection-parity.md @@ -68,8 +68,14 @@ rule allows. The price is the reason the issue stayed open rather than something service's typo now refuses the file for every target in it. Both documents moved out of a residual catalogue and into `tests/conformance/corpus/`, where `assert_rule` -- which raises on exactly that combination -- is what holds them closed, so the rule is hard everywhere with nothing suspended. -What remains open is a limitation rather than a residual: the drive-qualified *bind* -(`C:\data:/var`), since podman mounts that source through `--mount` and only the short `-v` spec -cannot spell it -- the long form already emits `--mount`, so the capability is reachable today and -only the short spelling is missing -([#111](https://github.com/modern-python/compose2pod/issues/111)). +One over-rejection is settled rather than open: the drive-qualified *bind* (`C:\data:/var`). +podman mounts that source through `--mount` and only the short `-v` spec cannot spell it, so the +capability is reachable today -- the long form emits exactly the invocation measured at exit 0, +and a `LIMITATIONS` row asserts it continuously. What was left was the ergonomic question, and +[#111](https://github.com/modern-python/compose2pod/issues/111) closed it as working as intended: +on Linux that spelling overwhelmingly means a Windows user pointed at a drive that is +not there, and falling back to `--mount` would bind a relative directory literally named +`C:\data`, surfacing much later as an empty mount instead of at once as an error naming the long +form. So the refusal is the tool, not a gap waiting to be filled. What would reopen it is a real +document wanting a colon in a short-form bind source on Linux, which is the evidence +[#86](https://github.com/modern-python/compose2pod/issues/86) never had. diff --git a/tests/conformance/conftest.py b/tests/conformance/conftest.py index dc9b7e2..4a44d2c 100644 --- a/tests/conformance/conftest.py +++ b/tests/conformance/conftest.py @@ -65,7 +65,9 @@ def pytest_terminal_summary(terminalreporter: pytest.TerminalReporter) -> None: terminalreporter.write_line(label) terminalreporter.write_line( f"{len(over_rejections)} over-rejection(s) -- catalogued limitations, not failures; " - "cross-check against the open limitation issues" + "each is ruled on in docs/adr/0003-the-shared-namespace-decides-key-classification.md " + "or docs/adr/0006-docker-rejection-parity.md, and one with no ruling there is the thing " + "to chase" )