nativegate 0.1.3__tar.gz → 0.1.5__tar.gz

{nativegate-0.1.3 → nativegate-0.1.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nativegate
-Version: 0.1.3
+Version: 0.1.5
 Summary: Make legacy C++/C/Fortran AI-ready and microservice-ready: expose native code as an MCP server, REST API and container
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown

{nativegate-0.1.3 → nativegate-0.1.5}/nativegate/config.py

@@ -805,6 +805,26 @@ class ServiceConfig:
                 "Run `ngate create-service` first."
             )
         data = yaml.safe_load(config_path.read_text()) or {}
+        # Unknown top-level keys are an error, not dead weight. A new
+        # nativegate.yaml key read by an older nativegate (the exact case
+        # this project shipped CI against: `dialect: cd` under a nativegate
+        # that pre-dated it) would otherwise vanish the same way a letter
+        # transposed in `dialete:` would — the service generates from an
+        # assumption the user never wrote.
+        known_keys = {
+            "name", "language", "expose", "parser", "clang", "libraries",
+            "include_paths", "api", "dialect",
+            "fortran",  # namespace for fortran.defines
+            # verification layer 3 keys
+            "state", "invariants", "ranges", "lattice",
+        }
+        unknown = sorted(set(data) - known_keys)
+        if unknown:
+            raise ConfigError(
+                f"{config_path}: unknown key(s) {', '.join(unknown)}. "
+                "Check the spelling against this nativegate version's supported "
+                "keys, or upgrade nativegate if the key is new."
+            )
         expose = _load_expose(data.get("expose"), config_path)
         clang_data = data.get("clang") or {}
         # `None` means "no restriction": `expose: all` or an empty `expose:`

{nativegate-0.1.3 → nativegate-0.1.5}/nativegate/parsers/dialect.py

@@ -41,7 +41,15 @@ import re
 
 DIALECT_CHOICES = ("cs", "cd")
 
-_PREFIX_RE = re.compile(r"^(CS|CD)(?=[ \t])", re.IGNORECASE | re.MULTILINE)
+# Statement labels are dialect-marked too ("CD900 DGAMMA = RES"), so no
+# space lookahead: any line starting with CS/CD is prefix-marked, with a
+# following space, tab, digit or line end allowed out to avoid tripping
+# on prose comments like "CSIMPLER". A live statement never starts with
+# literal letters in column 1 — the statement field begins in column 7 —
+# so there is no legitimate Fortran that begins "CS"/"CD" here. A comment
+# that merely starts with those letters is, at worst, re-marked; the
+# only real hazard would be more labels lost to a stricter pattern.
+_PREFIX_RE = re.compile(r"^(CS|CD)(?=[ \t\n]|\d|$)", re.IGNORECASE | re.MULTILINE)
 
 
 def resolve_dialect(raw: str | None) -> str:

{nativegate-0.1.3 → nativegate-0.1.5}/nativegate.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nativegate
-Version: 0.1.3
+Version: 0.1.5
 Summary: Make legacy C++/C/Fortran AI-ready and microservice-ready: expose native code as an MCP server, REST API and container
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown

{nativegate-0.1.3 → nativegate-0.1.5}/nativegate.egg-info/SOURCES.txt

@@ -57,6 +57,7 @@ tests/test_cli_serve_verify.py
 tests/test_cli_suggest.py
 tests/test_cli_verify_aggregate.py
 tests/test_cmake_gen.py
+tests/test_config_unknown_keys.py
 tests/test_cpp_ast.py
 tests/test_cpp_driver.py
 tests/test_cpp_pipeline.py

{nativegate-0.1.3 → nativegate-0.1.5}/pyproject.toml

@@ -13,7 +13,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "nativegate"
-version = "0.1.3"
+version = "0.1.5"
 description = "Make legacy C++/C/Fortran AI-ready and microservice-ready: expose native code as an MCP server, REST API and container"
 readme = "README.md"
 requires-python = ">=3.10"

nativegate-0.1.5/tests/test_config_unknown_keys.py

@@ -0,0 +1,77 @@
+"""Unknown top-level keys in nativegate.yaml must fail loading.
+
+Found in the wild (2026-09-23): specfun-py's CI installed a nativegate
+that pre-dated the `dialect:` key and generated the service anyway from
+an assumption never written down — the unknown key was swallowed as dead
+weight. A typo in any key was equally silent. Now both are config errors
+that say what is wrong and what to do about it.
+"""
+
+import shutil
+import textwrap
+
+import pytest
+
+from nativegate.config import ConfigError, ServiceConfig
+
+
+@pytest.fixture()
+def scratch(tmp_path, monkeypatch):
+    service = tmp_path / "demo"
+    (service / "native").mkdir(parents=True)
+    monkeypatch.chdir(tmp_path)
+    return service
+
+
+def _config_for_lines(text):
+    def _load(service):
+        (service / "nativegate.yaml").write_text(text)
+        return ServiceConfig.load(service)
+    return _load
+
+
+def test_unknown_key_is_an_error(scratch):
+    (scratch / "nativegate.yaml").write_text(textwrap.dedent("""\
+        name: demo
+        language: fortran
+        diatect: cd
+        expose:
+          functions: []
+        """))
+    with pytest.raises(ConfigError) as exc:
+        ServiceConfig.load(scratch)
+    assert "diatect" in str(exc.value)
+    assert "upgrade nativegate" in str(exc.value)
+
+
+def test_future_key_is_a_config_error_not_a_silent_noop(scratch):
+    (scratch / "nativegate.yaml").write_text(textwrap.dedent("""\
+        name: demo
+        language: fortran
+        dialect: cd
+        expose:
+          functions: []
+        """))
+    # fine on a nativegate that knows the key
+    config = ServiceConfig.load(scratch)
+    assert config.dialect == "cd"
+
+
+def test_all_declared_keys_still_load(scratch):
+    (scratch / "nativegate.yaml").write_text(textwrap.dedent("""\
+        name: demo
+        language: fortran
+        dialect: cd
+        parser: auto
+        libraries:
+        - petro
+        include_paths: []
+        fortran:
+          defines: []
+        expose:
+          all: true
+        """))
+    config = ServiceConfig.load(scratch)
+    assert config.dialect == "cd"
+    assert config.libraries == ["petro"]
+    assert config.expose.all is True

{nativegate-0.1.3 → nativegate-0.1.5}/tests/test_dialect.py

@@ -45,10 +45,42 @@ CD    DOUBLE PRECISION
      1    C,CONV,EPS
       DGAMMA = 24.0D0
       RETURN
+C the labelled assignment is dialect-marked as well: label in cols 1-5,
+C prefix occupying cols 1-2, so the 9 lands in column 3 — still inside
+C the label field (columns 1-5) after two blanks are substituted.
+900   DGAMMA = 24.0D0
+      RETURN
+      END
+""")
+
+DUAL_WITH_MARKED_LABEL = textwrap.dedent("""\
+CD    DOUBLE PRECISION FUNCTION DGAMMA(X)
+CS    REAL FUNCTION GAMMA(X)
+      GO TO 900
+CD900 DGAMMA = 24.0D0
+CS900 GAMMA = 24.0E0
+      RETURN
+900   CONTINUE
+      RETURN
       END
 """)
 
 
+def test_apply_dialect_marks_statement_labels_too():
+    """`CD900 DGAMMA = ...` is the line that exposed the strict space-lookahead
+    regex: labels start at column 1 and the prefix replaces its first two
+    characters, so the following character is a digit, not a space. A
+    space-lookahead regex would leave the label line inert and the resolved
+    file compiles with "label 900 referenced but never defined"."""
+    out = apply_dialect(DUAL_WITH_MARKED_LABEL, "cd")
+    lines = out.splitlines()
+    # label survives in the label field (digits starting column 3 is legal)
+    assert "  900 DGAMMA = 24.0D0" in lines
+    # the CS half is commented, label included
+    assert "C 900 GAMMA = 24.0E0" in lines
+    assert "C     REAL FUNCTION GAMMA(X)" in lines
+
+
 def test_apply_dialect_selects_cd():
     out = apply_dialect(DUAL_DIALECT, "cd")
     lines = out.splitlines()