Fluksio/app - app

497 Commits 1 Branch 6 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Fable 5.1	3397739c14	Refuse a port the function cannot take, and read a failing node as degraded Docs / docs (push) Successful in 33s Details Playwright Tests / test-playwright (1, 2) (push) Failing after 1m26s Details Playwright Tests / test-playwright (2, 2) (push) Failing after 15s Details pre-commit / pre-commit (push) Failing after 1m43s Details Test Backend / test-backend (push) Failing after 2m46s Details Compose Smoke Test / test-compose (push) Failing after 12s Details Playwright Tests / merge-reports (push) Canceled after 0s Details A python node's ports and settings arrive as keyword arguments, so a declared name its `process` does not take was a TypeError on every call — and a node that loads fine and fails every time it runs is the quiet kind of broken: the hosted demo did it 720 times an hour for two days and the health badge read ok throughout. `_build_node` now reads a written body with `ast` and refuses the mismatch at load, so the node is an error on the canvas and an issue on publish. Skipped for `kwargs`, a decorated or absent `process`, and the template a new node opens with. The SDK's generated shim always takes `settings`, so synced flows are untouched. `/observability/summary` names a node that has failed in the last fifteen minutes and reads degraded while it does, which is what would have made the badge amber. `nodes.failing` carries the count. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SkgNtaR6JspnHBFFP6crZj	2026-09-02 22:37:44 +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
stroblmeandClaude Opus 5	3508713e85	Node settings arrive as keyword arguments, not a params dict A python node's settings are constants of its own function, so they are passed the way its ports are: by name. The controller binds them to the compiled function, the `params` field is gone from the worker and remote protocols, and a setting sharing a port's name is reported as a node error rather than shadowing it. The panel's scaffold follows suit and keeps the header in step with both ports and settings. The demo's `pace` moves from a flow input to a setting of the training node, which is what it always was. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NUb8YpL2s3gmN9WTACTt4q	2026-08-20 17:47:45 +02:00

Author

SHA1

Message

Date

stroblmeandClaude Fable 5.1

3397739c14

Refuse a port the function cannot take, and read a failing node as degraded

Docs / docs (push) Successful in 33s

Details

Playwright Tests / test-playwright (1, 2) (push) Failing after 1m26s

Details

Playwright Tests / test-playwright (2, 2) (push) Failing after 15s

Details

pre-commit / pre-commit (push) Failing after 1m43s

Details

Test Backend / test-backend (push) Failing after 2m46s

Details

Compose Smoke Test / test-compose (push) Failing after 12s

Details

Playwright Tests / merge-reports (push) Canceled after 0s

Details

A python node's ports and settings arrive as keyword arguments, so a declared
name its `process` does not take was a TypeError on every call — and a node
that loads fine and fails every time it runs is the quiet kind of broken: the
hosted demo did it 720 times an hour for two days and the health badge read
ok throughout. `_build_node` now reads a written body with `ast` and refuses
the mismatch at load, so the node is an error on the canvas and an issue on
publish. Skipped for `**kwargs`, a decorated or absent `process`, and the
template a new node opens with. The SDK's generated shim always takes
`**settings`, so synced flows are untouched.

`/observability/summary` names a node that has failed in the last fifteen
minutes and reads degraded while it does, which is what would have made the
badge amber. `nodes.failing` carries the count.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SkgNtaR6JspnHBFFP6crZj

2026-09-02 22:37:44 +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

stroblmeandClaude Opus 5

3508713e85

Node settings arrive as keyword arguments, not a params dict

A python node's settings are constants of its own function, so they are passed
the way its ports are: by name. The controller binds them to the compiled
function, the `params` field is gone from the worker and remote protocols, and
a setting sharing a port's name is reported as a node error rather than
shadowing it. The panel's scaffold follows suit and keeps the header in step
with both ports and settings.

The demo's `pace` moves from a flow input to a setting of the training node,
which is what it always was.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NUb8YpL2s3gmN9WTACTt4q

2026-08-20 17:47:45 +02:00