• v0.17.6 40ec3f563f

    v0.17.6 Stable

    x released this 2026-11-08 00:05:13 +00:00 | 11 commits to main since this release

    VSKI v0.17.6 — Plugin gates, containers hardening

    Gates — the platform's named HTTP endpoints — can now target plugin
    functions natively
    (url: plugin://<instance>/<function>): the
    caller's JSON body is dispatched as the function's params over the warm
    plugin pipe and the result comes back verbatim. This replaces the
    credential-injecting HTTP bridge as the way to expose one plugin
    function to selected callers, and closes that pattern's hole where any
    caller passing the gate rule could invoke any function on the
    instance. The containers plugin gets the hardening pass from its
    official-plugin review.

    Safe upgrade: no schema migrations and no configuration changes; gates
    with http(s):// targets behave exactly as before. No SDK changes —
    the call side (client.gate(name, body)) was already generic.

    Gates: plugin:// targets

    A gate whose url is plugin://<instance>/<function> dispatches
    directly into the running plugin instance:

    • The request body becomes the function's params — it must be a
      JSON object (an empty body is an empty object); anything else is a
      400.
    • The function's return value is the response body, verbatim (200).
    • The function identity is fixed by the gate record — callers pick
      the payload, never the function. Anyone a gate rule lets through can
      do exactly one thing; no plugin admin key is involved at any point.
    • Dispatch rides the warm stdio pipe (no loopback HTTP hop) under the
      standard invoke budget (30 s default, 120 s hard cap). The instance
      must be running — 502 with the reason otherwise, as with invoke
      failures and disabled plugins.
    • The instance is looked up in the caller's database (x-dbname
      header, default default), and the gate's access rule is checked
      exactly as for HTTP targets before anything is dispatched.

    The web console's gate form accepts plugin:// URLs (validated, with
    an inline hint), and the platform wiki gained a dedicated Gates
    page — model, CRUD via the _gates records API, proxy semantics and
    their caveats (no timeout, no streaming, buffered bodies), plugin
    targets, and security notes. The MCP guide now leads with plugin://
    targets and keeps the old admin-key bridge documented as a compatibility
    pattern, with its caller-picks-the-function caveat spelled out.

    Containers plugin: official-plugin hardening

    • Adoption no longer resets the timeout. Docker reports container
      times as RFC3339Nano (up to nine fractional digits), which the
      timestamp parser rejected on older supported Pythons — an adopted
      running container silently got a fresh full timeout budget after every
      plugin restart. All timestamps now parse through one normalizing
      helper (naive values read as UTC).
    • Undeliverable completion signals give up. A completed job whose
      workflow run was deleted server-side used to retry its signal forever
      and pin its record against retention. Signals now retry for
      signal_retry_hours (new instance config, default 24; 0 = never
      retry), after which the record is marked signalGaveUp and becomes
      reclaimable. An attempt-count cap guards against tight retry loops.
    • The prune sweep never touches a live job's container. Containers
      whose job record is still queued or running are skipped regardless of
      age — previously a legitimately long job (a max_timeout above the
      sweep age) could be force-removed mid-run.
    • network: host and network: container:<id> are rejected — they
      defeat the isolation the plugin promises; user-defined Docker
      networks only.
    • Duplicate dispatches can no longer create two jobs — the
      find-or-create path of container.start is serialized.
    • Per-job runtime state (locks, cancel events) is released once a
      job completes and its signal settles, instead of accumulating for the
      process lifetime.
    • The distribution image pins vski-sdk 0.15.0 (Makefile venv and
      requirements floor alike), so the plugin's stats collector actually
      registers in the shipped image — with the previous 0.14.0 pin the
      feature silently no-oped.

    All of the above is covered by new unit tests (timestamp table,
    adoption-timeout with nanosecond stamps, give-up both ways, prune
    sparing live jobs, state release, concurrent start) and the full unit +
    end-to-end suites pass.

    Downloads