Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
320 Commits 1 Branch 6 Tags
93374a310ed60f9d07cee42fac395e2c5cb5cb66
Commit Graph
4 Commits
Author SHA1 Message Date
stroblmeandClaude Opus 5 400d7d9c5c Stage caching for batch runs, and an engine that lives in the command
Docs / docs (push) Successful in 19s
Details
Playwright Tests / test-playwright (1, 2) (push) Failing after 1m5s
Details
Playwright Tests / test-playwright (2, 2) (push) Failing after 20s
Details
pre-commit / pre-commit (push) Failing after 2m33s
Details
Test Backend / test-backend (push) Successful in 2m7s
Details
Compose Smoke Test / test-compose (push) Failing after 20s
Details
Playwright Tests / merge-reports (push) Failing after 1m3s
Details
Publish / publish (push) Failing after 12s
Details 
A code node in a batch run is now fingerprinted by its source, its raw
settings and the values it reads — an artifact input counting as its digest,
which is what the content addressing was always for. A run that finds the key
restores what the earlier one returned and skips the node, recorded as
`cached`. The run history is the cache: `run_node.outputs` beside the
`cache_key` the schema already had, no second store. On for code nodes, never
for the built-in and connector types that have side effects; off per node with
`@node(cache=False)` and per run with `--no-cache`.

Emissions are not replayed on a hit, so a cached training node returns its
result without redrawing its curve. Recorded in NOTEPAD.md with the two other
deliberate limits.

`fluksio run --local` boots the real app in the command's own process and
drives it through its ASGI interface behind the ordinary client, so a run no
longer needs a `serve` terminal beside it — same data directory, same history,
and the cache carries between the two. It always waits, because the engine it
starts lives exactly as long as the command.

Also: `fluksio sweep --param lr=0.1,0.01` for the product of the lists,
`run --follow` for a run's numbers as they arrive, Ctrl-C cancelling a waited
run rather than abandoning it, coloured statuses on a terminal, and `name`
made optional on the metrics endpoint so a follower can ask for every series.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
 2026-08-24 20:31:31 +02:00
stroblmeandClaude Opus 5 32bc0a5e66 Say a rebuild has two scopes, and close the notepad items it fixes 
The module docstrings and the notepad still described one rebuild that
touches everything. Closes the toggle cost, the seeding cost, the
per-save rebuild, the modules/apply rebuild and the Playwright spec that
could not fit a rebuild into its five seconds; files the follow-ups the
refactor leaves behind.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu
 2026-08-23 19:05:23 +02:00
stroblmeandClaude Opus 5 294b72d989 Let a pipeline swap one flow's nodes instead of being rebuilt 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu
 2026-08-23 17:41:14 +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