Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SDK: artifacts work outside a node, run --follow prints status and queue waits, fluksio cancel

Browse Source 
save_artifact/load_artifact outside a node use the worker's own store code in
$FLUKSIO_ARTIFACT_DIR or <tmp>/fluksio-artifacts, so a node can be called by
hand. --follow prints status changes and each node's resource wait; the
placer's waiting snapshot now carries the run. fluksio cancel <run>...

Claude-Session: https://claude.ai/code/session_01SSi5AvZ7pFmySK8zy3NPMh
This commit is contained in:
stroblme
2026-10-28 08:07:35 +01:00
parent a4393381ab
commit 6b8473f207
14 changed files with 274 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/code/nodes.md
+4 -2
View File
@@ -110,8 +110,10 @@ def process():
```
Another node can read it with `fluksio.load_artifact(report)`, which returns
a local file path. These two helpers require a running node; for tests,
keep the underlying calculation in ordinary Python functions.
a local file path. Called directly, outside a node, the two helpers store the
bytes in `$FLUKSIO_ARTIFACT_DIR` or, when that is unset, in `fluksio-artifacts`
under the temporary directory. The reference has the same shape as inside the
engine, so a test can pass what one node returns to the next.
Artifacts are stored by their SHA-256 digest, so identical bytes share storage.
Use [`fluksio artifacts`](cli.md#fluksio-artifacts) to list and download a