nativegate 0.1.4__tar.gz → 0.1.6__tar.gz

{nativegate-0.1.4 → nativegate-0.1.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nativegate
-Version: 0.1.4
+Version: 0.1.6
 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.4 → nativegate-0.1.6}/nativegate/generators/f2py_gen.py

@@ -67,6 +67,24 @@ set(F2PY_SOURCES
 {sources}
 )
 
+# Say the fix, not the symptom: when this tree is consumed without
+# `ngate generate` having run (a packaging commit that ships the service
+# tree without native/_expanded), ninja would otherwise die mid-configure
+# with "no known rule to make it", which hides the remedy one exception
+# down a build log. Confirmed in the wild as DEFECTS D11, via
+# ravikings/specfun-py's first CI run.
+foreach(f2py_source IN LISTS F2PY_SOURCES)
+    if(NOT EXISTS "${{f2py_source}}")
+        message(FATAL_ERROR
+            "Missing build input: ${{f2py_source}}\n"
+            "nativegate generates this file when it resolves INCLUDE decks, "
+            "dialect marking and intent directives. Run:\n"
+            "    ngate generate {service_name}\n"
+            "from this service directory (or the repo root), then build again."
+        )
+    endif()
+endforeach()
+
 set(F2PY_OUTPUT "${{CMAKE_CURRENT_BINARY_DIR}}/{module.name}${{PY_EXT_SUFFIX}}")
 
 # f2py's meson backend picks tempfile.mkdtemp() for its build directory

{nativegate-0.1.4 → nativegate-0.1.6}/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.4 → nativegate-0.1.6}/nativegate.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nativegate
-Version: 0.1.4
+Version: 0.1.6
 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.4 → nativegate-0.1.6}/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_cmake_missing_input.py
 tests/test_config_unknown_keys.py
 tests/test_cpp_ast.py
 tests/test_cpp_driver.py

{nativegate-0.1.4 → nativegate-0.1.6}/pyproject.toml

@@ -13,7 +13,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "nativegate"
-version = "0.1.4"
+version = "0.1.6"
 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.6/tests/test_cmake_missing_input.py

@@ -0,0 +1,67 @@
+"""D11: a service tree consumed without `generate` must say so at configure
+time.
+
+The generated CMake references native/_expanded/ sources that `ngate
+generate` writes. A packaging commit that ships the service tree without
+them (the exact failure of specfun-py's first CI run) surfaced as ninja's
+"no known rule to make it" mid-build, with the remedy buried one exception
+down a log. The generated CMake now fatals at configure time with the
+remedy written out.
+"""
+
+import shutil
+import textwrap
+from pathlib import Path
+
+import pytest
+
+from nativegate.generators import f2py_gen
+
+
+def test_generated_cmake_carries_the_missing_input_guard():
+    cmake = f2py_gen.generate_cmake(
+        type("M", (), {"name": "specfun"})(),
+        "specfun",
+        ["native/_expanded/gamma.f"],
+    )
+    assert "foreach(f2py_source IN LISTS F2PY_SOURCES)" in cmake
+    assert "NOT EXISTS" in cmake
+    assert "ngate generate" in cmake
+
+
+@pytest.mark.skipif(shutil.which("cmake") is None, reason="cmake not on PATH")
+@pytest.mark.skipif(
+    shutil.which("gfortran") is None, reason="Fortran language check needs a compiler"
+)
+def test_guard_fires_when_the_input_file_is_absent(tmp_path):
+    cmake = f2py_gen.generate_cmake(
+        type("M", (), {"name": "specfun"})(),
+        "specfun",
+        ["native/_expanded/gamma.f"],
+    )
+    (tmp_path / "CMakeLists.txt").write_text(cmake)
+    (tmp_path / "native" / "_expanded").mkdir(parents=True)
+    (tmp_path / "native" / "_expanded" / "gamma.f").write_text(
+        textwrap.dedent("""\
+            MISSING
+            """)
+    )
+    (tmp_path / "native" / "_expanded" / "gamma.f").unlink()
+
+    result = _configure(tmp_path)
+    combined = result.stdout + result.stderr
+    assert "Missing build input" in combined
+    assert "ngate generate specfun" in combined
+    # and NOT the misleading ninja symptom
+    assert "no known rule to make it" not in combined
+
+
+def _configure(tmp_path):
+    import subprocess
+    import sys
+    env_path = sys.executable
+    return subprocess.run(
+        ["cmake", "-S", str(tmp_path), "-B", str(tmp_path / "build"),
+         f"-DPython_EXECUTABLE={env_path}"],
+        capture_output=True, text=True,
+    )

{nativegate-0.1.4 → nativegate-0.1.6}/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()