4 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	608d30d884	Let a node say how much of the machine it takes ... Five concurrent training nodes, each sizing its thread pool to every core, left the engine's own event loop unscheduled: the API stopped answering within 10 s and every client died. The same shape on a GPU deadlocked a run for 21 minutes at 0% utilisation with nothing failing and nothing to read -- it just sat in `running`. @node(resources={"cpus": 2}) is the declaration. The engine holds that much for the length of the execution, so more of them than the machine has room for wait their turn rather than oversubscribing it, and a `gpus` node holds its card exclusively. FLOW_CPUS defaults to every core but two, and those two are what keeps the engine answering. Because a thread cap is read when the process imports the library, a warm worker cannot be told a different one -- so an environment gets a pool of its own and nodes deriving the same one share it, rather than paying a cold start per call on exactly the nodes whose imports are slowest. XLA_FLAGS is never derived: it is a composed, version-dependent string, so it travels in resources.env where it is visible. A node that declares nothing is not accounted for and behaves as it always did -- it just gets FLOW_CPUS/FLOW_MAX_WORKERS as a thread cap, which is the half of this that fixes the reported incident without anybody declaring anything. An operator who set OMP_NUM_THREADS themselves still wins. Resources are claimed strictly before a worker slot, so the two blocking waits cannot deadlock. A node queued for them publishes node_queued and shows on GET /workers/resources, because waiting and hanging looked identical. Accounted, not enforced: no cgroups, no rlimits. Scheduling across machines, flavours and enforcement are the next steps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-26 21:36:59 +02:00
stroblmeandClaude Opus 5	d4a9406c51	Fix the CI gates: Python 3.13, concurrency groups, hook violations ... The gates have never gone green on the new runners. Three separate reasons: - backend/Dockerfile shipped Python 3.10 while the code imports typing.Self and datetime.UTC, so the container exited on import and the suite could not even load its conftest. The image moves to 3.13 and the packages declare >=3.12, which is the floor the tests actually pass on; ruff's target follows and rewrites timezone.utc and asyncio.TimeoutError accordingly. Relocking drops the 3.10 branch, which bumps FastAPI and so regenerates the SDK. - frontend/README.md had no trailing newline and two dashboard widgets used arbitrary text-[…] sizes. Both are em-relative on purpose, so they move to the inline style the neighbouring ramp already uses. - Every commit left its own run queued: without a concurrency group a runner that was offline for a while works through a backlog nobody reads. A stack that fails to come up now prints its logs before the teardown removes it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-24 14:55:59 +02:00
stroblmeandClaude Opus 5	2c369ac75f	Split the worker into a distribution of its own ... A cluster or GPU host installs `pip install fluksio-worker` and gets the agent and the runner, not psycopg, numpy and the MCP SDK. The engine depends on it as a workspace member, so the file it launches node code with is the same file a remote worker runs — which is what keeps a node unable to tell the difference. Copying the two files by hand still works. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 21:54:10 +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