com.blockether.vis.internal.loop.python-exec — com.blockether/vis 0.2.31

Execution of one model-written block in the session's persistent Python interpreter.

Rejects blocks that are not code, runs a block with timing and Activity reporting, interrupts and unwinds a runaway block, and retires a worker that does not unwind. policy-reload-epoch counts /reloads; environments built under an older epoch are replaced.

attachment-descriptor clj

(attachment-descriptor a)

One session_attachment row as the compact DESCRIPTOR list_attachments() and get_attachment(id) hand the model: identity, provenance and shape, and never any bytes.

PROVENANCE STARTS AT THE TURN. Every row carries session_turn_soul_id, so every descriptor carries :turn-id — a user image and a tool artifact are placed the same way and a rail can be grouped by turn without a second lookup. :iteration-id / :tool-call-id are the FINER grain only a tool artifact has, so a user image omits both instead of carrying nils that say nothing.

:is-pending is false here by construction: a stored row is stored. The sandbox reader answers the same key true for an artifact the RUNNING block just attached, which is not in the database yet.

execute-code clj

(execute-code environment code & {:keys [timeout-ms tool-event-fn]})

Run a single :code block through the Python sandbox.

Optional kwargs: :timeout-ms - hard-cap eval time, clamped at the rt/eval-timeout-ms bounds.

Every call performs a real Python eval. There is no result cache: forms with side effects MUST run their bodies on every invocation, and forms without side effects re-run cheaply enough that caching them is not worth the correctness footgun.

get-locals clj

(get-locals _environment)

User-defined sandbox vars surface. Live-vars introspection is cosmetic-off for the Python engine (the agent uses its own Python scope + stdlib), so this returns an empty map. Kept as a stable seam for the trailer/renderer callers.

literal-code-block-error clj

(literal-code-block-error python-context expr)

policy-reload-epoch clj

Monotonic /reload epoch. Every /reload bumps it (via a reload hook). Stale idle sandboxes close immediately; busy ones close after their turn. The next turn rebuilds the immutable security-policy snapshot from the freshly-reloaded vis.yml. This is the sanctioned way /reload replaces the frozen network-domain / filesystem-root policy: the snapshot drives the Python session, egress proxy, and process jail at env-creation time, so it can only change by rebuilding the env — never by an in-place reseat.

retire-python-context-once! clj

(retire-python-context-once! python-context environment reason error)

Kill one abandoned environment's Python process at most once. Process teardown does not enter the interpreter, so it is safe even while the turn thread still owns the environment lock.