hypernix 0.72.4.post3__tar.gz → 0.72.4.post12__tar.gz

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/.github/workflows/ios.yml

@@ -36,12 +36,20 @@ on:
         description: "Run the unit tests on a simulator"
         type: boolean
         default: true
+      local_engine:
+        description: "Build llama.cpp into the app so it can run models on-device. Adds 15-25 minutes."
+        type: boolean
+        default: false
   workflow_call:
     inputs:
       run_tests:
         description: "Run the unit tests on a simulator"
         type: boolean
         default: false
+      local_engine:
+        description: "Build llama.cpp into the app so it can run models on-device."
+        type: boolean
+        default: false
       version:
         description: "Marketing version to stamp into the build"
         type: string
@@ -118,12 +126,36 @@ jobs:
           echo "build=${GITHUB_RUN_NUMBER}" >> "$GITHUB_OUTPUT"
           echo "::notice::HyperLink $marketing (build ${GITHUB_RUN_NUMBER})"
 
+      # Off by default, and deliberately so: it clones llama.cpp and
+      # compiles it for two slices, which is 15-25 minutes on a hosted
+      # macOS runner and is not worth paying on a PR that touched a
+      # view. Without it the app builds and ships with EchoRunner,
+      # which tells the user this build has no local engine.
+      - name: Build the inference engine
+        if: ${{ inputs.local_engine }}
+        working-directory: ios
+        run: |
+          set -euo pipefail
+          ./scripts/build_llama_xcframework.sh
+          echo "--- what was built ---"
+          cat vendor/llama.xcframework.json
+          echo "--- the flag the project reads ---"
+          cat vendor/LocalLlama.xcconfig
+
       - name: Generate the Xcode project
         working-directory: ios
         run: |
           set -euo pipefail
           xcodegen generate --spec project.yml
           ls -la HyperLink.xcodeproj
+          # Say which of the two builds this is, in the log, where
+          # someone reading a failure will look. An app that silently
+          # has no engine is the confusing case.
+          if grep -q 'HNX_LOCAL_LLAMA = HNX_LOCAL_LLAMA' vendor/LocalLlama.xcconfig; then
+            echo "::notice::on-device inference is ON (llama.cpp linked)"
+          else
+            echo "::notice::on-device inference is OFF — EchoRunner only"
+          fi
 
       - name: Do we have signing secrets?
         id: signing

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/.github/workflows/public-release.yml

@@ -136,55 +136,26 @@ jobs:
           pip install --index-url https://download.pytorch.org/whl/cpu torch
           pip install -e ".[dev]"
 
-      - name: Refuse a version that goes backwards
-        # This workflow writes whatever version it is handed, so a
-        # dispatch naming an older one silently downgrades main. It has
-        # happened: v0.72.3.post2 was dispatched against a tree already
-        # at 0.72.3.post4 and rewrote all three version strings to the
-        # older number, leaving main claiming a release that predates the
-        # code in it. Nothing downstream can detect that -- the built
-        # wheel is internally consistent, it is just wrong about which
-        # release it is.
-        if: ${{ !inputs.allow_downgrade }}
+      - name: Check the version this release was dispatched with
+        # Three questions, and the old inline guard conflated two of
+        # them. It refused a version equal to the tree's outright --
+        # "already what the tree says, use a .postN suffix" -- but
+        # preparing a release *is* writing that version into the three
+        # source files and adding the changelog heading under it, and
+        # both steps below already expect it: the commit step notices
+        # there is nothing to commit and the tag step skips a tag that
+        # exists. Only the guard disagreed, and the cost was paid in the
+        # changelog: 0.72.4 post1 and post3 were cut under numbers
+        # invented at dispatch time to get past it, so neither has a
+        # heading and neither says what shipped.
+        #
+        # What actually makes a repeat unsafe is the number naming other
+        # code, which a version string cannot tell you and a tag can.
+        # See .github/scripts/version_guard.py -- it is a script rather
+        # than a heredoc so tests/test_version_guard.py can drive it.
         run: |
-          python - <<'GUARD'
-          import re, sys
-          from pathlib import Path
-          from packaging.version import Version, InvalidVersion
-
-          requested = "${{ inputs.version }}"
-          pep440 = requested.replace("postr", "post")
-          if re.fullmatch(r"\d+\.\d+\.\d+-\d+", pep440):
-              base, build = pep440.rsplit("-", 1)
-              pep440 = f"{base}.post{build}"
-
-          current = re.search(
-              r'^version = "([^"]+)"', Path("pyproject.toml").read_text(), re.M
-          )
-          if current is None:
-              sys.exit("::error::no version line in pyproject.toml")
-
-          try:
-              new, old = Version(pep440), Version(current.group(1))
-          except InvalidVersion as exc:
-              sys.exit(f"::error::{exc}")
-
-          if new > old:
-              print(f"{old} -> {new}")
-          elif new == old:
-              sys.exit(
-                  f"::error::version {new} is already what the tree says. "
-                  f"Re-releasing the same number publishes different code "
-                  f"under one version. Use a .postN suffix."
-              )
-          else:
-              sys.exit(
-                  f"::error::version {new} is OLDER than the tree's {old}. "
-                  f"Publishing it would make main claim a release that "
-                  f"predates its own code. If you really mean to roll back, "
-                  f"re-run with allow_downgrade."
-              )
-          GUARD
+          python .github/scripts/version_guard.py '${{ inputs.version }}' \
+            ${{ inputs.allow_downgrade && '--allow-downgrade' || '' }}
 
       - name: Bump versions in source
         run: |

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hypernix
-Version: 0.72.4.post3
+Version: 0.72.4.post12
 Summary: Download and quantize the HyperNix PyTorch model to GGUF (fp32/fp16/Q8_0/Q6_K/Q4_K_M).
 Home-page: https://github.com/trail-b1az3r/hypernix-pip
 Author: HyperNix contributors
@@ -78,7 +78,7 @@ Dynamic: license-file
 </p>
 
 <p align="center">
-  <img alt="PyPI" src="https://img.shields.io/badge/PyPI-v0.72.4.post1-ff2d55?style=for-the-badge&logo=pypi&logoColor=white" />
+  <img alt="PyPI" src="https://img.shields.io/badge/PyPI-v0.72.4.post3-ff2d55?style=for-the-badge&logo=pypi&logoColor=white" />
   <img alt="Python" src="https://img.shields.io/badge/Python-3.10--3.14-00c9ff?style=for-the-badge&logo=python&logoColor=white" />
   <img alt="License" src="https://img.shields.io/badge/License-HOS%20/%20LLU-00c853?style=for-the-badge" />
 </p>

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/README.md

@@ -4,7 +4,7 @@
 </p>
 
 <p align="center">
-  <img alt="PyPI" src="https://img.shields.io/badge/PyPI-v0.72.4.post1-ff2d55?style=for-the-badge&logo=pypi&logoColor=white" />
+  <img alt="PyPI" src="https://img.shields.io/badge/PyPI-v0.72.4.post3-ff2d55?style=for-the-badge&logo=pypi&logoColor=white" />
   <img alt="Python" src="https://img.shields.io/badge/Python-3.10--3.14-00c9ff?style=for-the-badge&logo=python&logoColor=white" />
   <img alt="License" src="https://img.shields.io/badge/License-HOS%20/%20LLU-00c853?style=for-the-badge" />
 </p>

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/bin/hypernix-t1

@@ -19,7 +19,7 @@
 
 set -euo pipefail
 
-VERSION="0.72.3.post3"
+VERSION="0.72.4.post12"
 
 CONFIG_DIR="${T1_CONFIG_DIR:-$HOME/.hypernix/t1api}"
 ENV_FILE="$CONFIG_DIR/.env"
@@ -165,6 +165,88 @@ wait_healthy() {
   return 1
 }
 
+# ---------------------------------------------------------------------------
+# Detaching
+# ---------------------------------------------------------------------------
+
+spawn_detached() {
+  # spawn_detached PYTHON LOGFILE ARGS... -- start ARGS in a new session
+  # and print the pid of the process that is actually running it.
+  #
+  # This used to be `setsid "$py" -m uvicorn ... &` with `echo $!` for the
+  # pid, and that was wrong twice over.
+  #
+  # macOS has no `setsid` binary. The script advertises bash 3.2, which
+  # is the bash macOS ships, so macOS is a supported platform -- and
+  # there `setsid` is "command not found", the background job dies at
+  # once, `echo $!` still succeeds so the `|| die` guard never fires, and
+  # the only sign is a raw shell error in the log 45 seconds later.
+  #
+  # And `$!` is not dependable even where setsid exists: setsid(1) forks
+  # when it is already a process-group leader and the parent then exits,
+  # so the pid recorded can belong to a process that has already gone.
+  # `launch-script` hit exactly that and reported "unknown" for jobs that
+  # were running perfectly well; see _launch_setsid in
+  # hypernix/system/launcher.py.
+  #
+  # Python is already a hard requirement here -- it is the thing being
+  # launched -- and Popen(start_new_session=True) calls setsid(2) in the
+  # child itself. Same new session, no fork in between, and the pid it
+  # reports is the server's own. stdin goes to /dev/null so a read after
+  # the terminal is gone cannot raise EIO.
+  local py="$1" log="$2"; shift 2
+  HNX_T1_LOG="$log" "$py" -c '
+import os, subprocess, sys
+
+log = os.environ["HNX_T1_LOG"]
+with open(log, "ab") as handle:
+    proc = subprocess.Popen(
+        sys.argv[1:],
+        stdin=subprocess.DEVNULL, stdout=handle, stderr=handle,
+        start_new_session=True,
+    )
+print(proc.pid)
+' "$@"
+}
+
+logind_kills_user_processes() {
+  # systemd-logind with KillUserProcesses=yes kills everything the user
+  # owns at logout, a new session included. setsid(2) does not protect
+  # against it and nothing in the log explains the disappearance -- the
+  # server is simply gone the next time someone looks. Lingering is the
+  # exemption, so a machine that has it on is not affected.
+  command -v loginctl >/dev/null 2>&1 || return 1
+  local linger
+  linger="$(loginctl show-user "$(id -un)" --property=Linger --value 2>/dev/null || true)"
+  [ "$linger" = "yes" ] && return 1
+  local setting=""
+  if command -v busctl >/dev/null 2>&1; then
+    # The running configuration, which is what actually decides. Drop-ins
+    # under logind.conf.d override the main file, so reading only
+    # /etc/systemd/logind.conf can answer the wrong question.
+    setting="$(busctl --no-pager get-property org.freedesktop.login1 \
+      /org/freedesktop/login1 org.freedesktop.login1.Manager \
+      KillUserProcesses 2>/dev/null || true)"
+    case "$setting" in
+      *true) return 0 ;;
+      *false) return 1 ;;
+    esac
+  fi
+  # No busctl: fall back to the files, newest drop-in last.
+  local file value=""
+  for file in /etc/systemd/logind.conf /etc/systemd/logind.conf.d/*.conf \
+              /run/systemd/logind.conf.d/*.conf /usr/lib/systemd/logind.conf.d/*.conf; do
+    [ -r "$file" ] || continue
+    local found
+    found="$(sed -n 's/^[[:space:]]*KillUserProcesses[[:space:]]*=[[:space:]]*\([^[:space:]#]*\).*/\1/p' "$file" | tail -n 1)"
+    [ -n "$found" ] && value="$found"
+  done
+  case "$value" in
+    yes|true|1|on) return 0 ;;
+    *) return 1 ;;
+  esac
+}
+
 cmd_start() {
   load_env; require_installed
   local existing; existing="$(server_pid || true)"
@@ -182,14 +264,24 @@ cmd_start() {
 
   mkdir -p "$CONFIG_DIR"
   say "Starting the T1 API on ${host}:${port}…"
-  # setsid so the server outlives this shell; without it, closing the
-  # terminal takes the server with it.
-  ( setsid "$py" -m uvicorn hypernix.t1api.app:create_app --factory \
-      --host "$host" --port "$port" >>"$LOG_FILE" 2>&1 &
-    echo $! > "$PID_FILE" ) || die "Could not start the server."
+  local pid=""
+  pid="$(spawn_detached "$py" "$LOG_FILE" \
+    "$py" -m uvicorn hypernix.t1api.app:create_app --factory \
+    --host "$host" --port "$port")" \
+    || die "Could not start the server."
+  case "$pid" in
+    ''|*[!0-9]*) die "Could not start the server (no pid from the launcher)." ;;
+  esac
+  printf '%s\n' "$pid" > "$PID_FILE"
 
   case "$(wait_healthy "$url" "$(setting T1_START_TIMEOUT 45)"; echo $?)" in
-    0) ok "Running (pid $(server_pid)) — $url" ;;
+    0) ok "Running (pid $(server_pid)) — $url"
+       if logind_kills_user_processes; then
+         warn "This machine's logind has KillUserProcesses=yes, so logging out"
+         warn "will kill the server even though it has its own session."
+         dim "     Survive logout:  hypernix-t1 autostart on"
+         dim "                      sudo loginctl enable-linger $(id -un)"
+       fi ;;
     2) rm -f "$PID_FILE"
        err "The server exited during startup. Last lines:"
        tail -n 20 "$LOG_FILE" >&2 || true

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "hypernix"
-version = "0.72.4.post3"
+version = "0.72.4.post12"
 description = "Download and quantize the HyperNix PyTorch model to GGUF (fp32/fp16/Q8_0/Q6_K/Q4_K_M)."
 readme = { file = "README.md", content-type = "text/markdown" }
 license = { text = "HOL-1.0" }
@@ -198,16 +198,15 @@ hypernix = ["py.typed", "webui_static/*", "*.js", "t1api/data/*.json"]
 # Ruff / pytest defaults (also duplicated in ruff.toml / pytest.ini so
 # editors pick them up regardless of project layout).
 # ---------------------------------------------------------------------------
-[tool.ruff]
-line-length = 100
-target-version = "py312"
-
-[tool.ruff.lint]
-select = ["E", "F", "I", "UP", "B"]
-ignore = ["E501"]
-
-[tool.ruff.lint.isort]
-known-first-party = ["hypernix"]
+# ruff is configured in ruff.toml, not here.
+#
+# There used to be a [tool.ruff] block in this file as well. Ruff reads
+# .ruff.toml, then ruff.toml, then pyproject.toml's [tool.ruff], and
+# stops at the first one it finds -- so with ruff.toml present, this
+# block had no effect and had drifted: it was missing the per-file E402
+# exemptions for the deprecated modules and the flake8-bugbear
+# extend-immutable-calls list FastAPI needs. Two configs where one is
+# silently dead is worse than either.
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/ruff.toml

@@ -28,11 +28,15 @@ extend-immutable-calls = [
     "fastapi.Cookie",
 ]
 
-# These deprecated shims intentionally print a warning before their
-# imports so the message fires even if the rest of the module fails
-# to load; that ordering is the point, not an oversight.
+# These deprecated modules intentionally announce themselves before
+# their imports, so the message fires even if the rest of the module
+# fails to load -- and, for the ones that import torch, without waiting
+# several seconds for it. That ordering is the point, not an oversight.
+# The announcement itself is hypernix.system.deprecation, which imports
+# nothing heavier than os, sys and warnings.
 [lint.per-file-ignores]
 "src/hypernix/data/mediocre_fridge.py" = ["E402"]
 "src/hypernix/evaluation/new_fridge.py" = ["E402"]
 "src/hypernix/system/old_fridge.py" = ["E402"]
 "src/hypernix/models/old_oven.py" = ["E402"]
+"src/hypernix/monitoring/tvtop.py" = ["E402"]

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/setup.cfg

@@ -1,6 +1,6 @@
 [metadata]
 name = hypernix
-version = 0.72.4.post3
+version = 0.72.4.post12
 description = Download and quantize the HyperNix PyTorch model to GGUF (fp32/fp16/Q8_0/Q6_K/Q4_K_M).
 long_description = file: README.md
 long_description_content_type = text/markdown

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/src/hypernix/__init__.py

@@ -63,7 +63,7 @@ import importlib.util
 import sys
 from typing import TYPE_CHECKING, Any
 
-__version__ = "0.72.4.post3"
+__version__ = "0.72.4.post12"
 DEFAULT_REPO_ID = "ray0rf1re/hyper-Nix.2"
 DEFAULT_MODEL = "qwen3.5-4b"  # New default model
 
@@ -534,6 +534,7 @@ _LAZY_ATTRS: dict[str, tuple[str, str | None]] = {
     'nano_nano': ('models.nano_nano', None),
     'brewer_adapter': ('models.brewer_adapter', None),
     'gather': ('data.gather', None),
+    'runtime_bridge': ('quant.runtime_bridge', None),
     'neo_oven': ('models.neo_oven', None),
     'monitor': ('training.monitor', None),
     'net': ('system.net', None),
@@ -541,7 +542,13 @@ _LAZY_ATTRS: dict[str, tuple[str, str | None]] = {
     'fusebox': ('system.fusebox', None),
     'nettrust': ('system.nettrust', None),
     'new_fridge': ('evaluation.new_fridge', None),
-    'new_oven': ('models.old_oven', 'new_oven'),
+    # 0.72.4.post9: neo_oven, not old_oven. The 0.71.5a2 notes said
+    # these shortcuts returned a NeoOven from that release on; the map
+    # was never moved, so `hypernix.preheat` kept resolving into a
+    # deprecated module and -- once that module started announcing
+    # itself properly -- told callers of the *top-level* API to stop
+    # using a module they had not imported.
+    'new_oven': ('models.neo_oven', 'new_oven'),
     'new_range': ('evaluation.new_range', None),
     'old_fridge': ('system.old_fridge', None),
     'old_oven': ('models.old_oven', None),
@@ -551,7 +558,7 @@ _LAZY_ATTRS: dict[str, tuple[str, str | None]] = {
     'pans': ('data.pans', None),
     'pepper_shaker': ('data.pepper_shaker', None),
     'plasma': ('monitoring.plasma', None),
-    'preheat': ('models.old_oven', 'preheat'),
+    'preheat': ('models.neo_oven', 'preheat'),
     'pressure_cooker': ('optimizers.pressure_cooker', None),
     'pressure_cooker_v3': ('optimizers.pressure_cooker_v3', None),
     'pressure_cooker_v4': ('optimizers.pressure_cooker_v4', None),

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/src/hypernix/data/mediocre_fridge.py

@@ -25,9 +25,15 @@ modification.
 """
 from __future__ import annotations
 
-from rich.console import Console
-
-Console().print("[bold red]WARNING: mediocre_fridge is deprecated. Please transition to neo_oven.[/]")
+from hypernix.system.deprecation import deprecated_module
+
+# Announced before the heavy imports below, so the notice reaches the
+# operator immediately rather than after torch has finished loading.
+deprecated_module(
+    "hypernix.data.mediocre_fridge",
+    instead="hypernix.models.neo_oven",
+    since="0.71.5a2",
+)
 
 import random
 from collections.abc import Sequence

{hypernix-0.72.4.post3 → hypernix-0.72.4.post12}/src/hypernix/evaluation/new_fridge.py

@@ -16,9 +16,15 @@ Each plotting function accepts an ``out_path``; no GUI is ever opened.
 """
 from __future__ import annotations
 
-from rich.console import Console
-
-Console().print("[bold red]WARNING: new_fridge is deprecated. Please transition to neo_oven.[/]")
+from hypernix.system.deprecation import deprecated_module
+
+# Announced before the heavy imports below, so the notice reaches the
+# operator immediately rather than after torch has finished loading.
+deprecated_module(
+    "hypernix.evaluation.new_fridge",
+    instead="hypernix.models.neo_oven",
+    since="0.71.5a2",
+)
 
 import re
 from collections.abc import Sequence