6 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	4a38c6ed31	Name the code a run ran, and let an interrupted sync finish ... Three faults with one root: the stored body of a code-defined node is an import shim, and nothing that mattered was ever read from the code itself. - The run stamp could not identify what ran. The shim imports whatever is on disk when the worker starts, and an uncommitted tree stamps <commit>-dirty for every run it ever produces. Run.code_digest hashes the repository's .py files, memoized on their stat state, and it is read again when the run is actually claimed -- so a sweep queued for hours records the code each of its runs executed, not the code that was there when it was submitted. - The stage cache adopted code that was too new. The fingerprint hashed the shim, which is invariant under any edit to the imported function or anything it calls into, so a re-run was served from cache and answered without the outputs the edit added. It now carries the repo digest and the node's declared ports. Every fingerprint changes once, which invalidates the existing cache; a canvas flow has no repository and keys as before. - An interrupted sync looked like a hand-edited canvas. The engine answers a new-node template for a node with no stored body, and the template carries no marker, so the drift check read "somebody edited this" and demanded --force -- for the one state that re-running the sync is the fix for. NodeSource.missing states the fact, and sync skips those and reuses the bodies it read instead of asking for each one twice. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-26 21:27:10 +02:00
stroblmeandClaude Opus 5	dd7db026e1	Announce an acknowledged node failure on the bus ... Clearing a node's last error on the engine published nothing, so a second browser kept the marker until its next snapshot. One event carries the qualified node; the receiving client drops the marker without refetching. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Gf7WaExcJ9bs3kfJXB3nK	2026-08-25 22:33:09 +02:00
stroblmeandClaude Opus 5	c95d0ca8f5	Publish, delete and module installs rebuild only what changed ... Publishing or deleting a flow now splices that one flow into the running graph instead of reconnecting every node in the installation, saving a shared node's source rebuilds the flows using it, and installing modules rebuilds only the flows holding a node that would not load. Renaming stays on the full rebuild — it rewrites message references in every other flow's document — and so does startup, which has no graph to splice into. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu	2026-08-23 18:32:51 +02:00
stroblmeandClaude Opus 5	084194f77b	Warm a worker before the node's clock starts, and refuse to delete a live flow ... A node's timeout now covers its body only: the pool loads the source into the worker it picked, off the node's budget, so imports that outlast the timeout no longer make a node impossible to run. Draft checks compile without caching, so saving does not evict what a busy node is serving calls from. Requests carry an id the worker echoes and the pool checks, a reply is encoded once, and the remote-exception cache is bounded. DELETE /flows/{name} answers 409 while the flow has a running or queued run, which is what was letting run_node rows outlive their run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu	2026-08-23 17:11:55 +02:00
stroblmeandClaude Opus 5	148d50f2bd	Grow a node with its ports, stop it flickering, draw what it reaches out to ... - A node's height follows the ports on its busiest side. It is a function of the document, so `layoutGraph` reserves exactly what is drawn and nothing measured is fed back into the layout. - The three status controls now sit in slots that are there whether the control is or not. A node running many times a second mounted and unmounted the stop button on every execution, resizing the card each time. - A port bound to another flow's message is drawn as a label, naming the node at the far end and its type. Only the opposite direction was answered before. The scan behind both is now cached on the store's commit counter rather than reading every flow per request. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016ZeGnqVsf5VHQqvz4HdUhN	2026-08-23 06:35:28 +02:00
stroblmeandClaude Opus 5	60d7ec81c0	Rename the import package app to fluksio ... A wheel whose top-level module is `app` collides with anything else in a user's venv, so the package that is about to be published takes the name it is published under. Only the Python package moves; the repo, the Docker WORKDIR and the compose project keep theirs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 21:48:05 +02:00