app/backend/fluksio/flow at b7f1d21712cd23eb428bdc3febe4d047bec115db - app

nodes

Engine holds for a rename: the pipeline refuses publish and inline cascades with EngineHeld once those running have finished, the execution service stops claiming and its timers once claimed cascades have finished; both wait without a limit, report what is busy and can be aborted. REST answers 503 with Retry-After, a device frame busy. Redis adds no longer wait for each other, only a queue hold waits for them

2026-11-02 20:21:17 +01:00

__init__.py

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

alert_ledger.py

Alerts: cooldowns survive a restart, and a connection must stay down a minute before it alerts

2026-10-28 12:46:42 +01:00

alerts.py

Rename orchestration, splice and routes: a Renamer runs one rename at a time, closing the gate, taking the controller lock and holding the engine, each waiting without a limit and saying what it waits for (summary rename status, rename_waiting); DELETE on the pending request or a closed connection calls it off until the journal begins (409 aborted); then journal, steps and audit, retried in the background on failure (503 completing); splice_renamed rebuilds the affected flows under the held lock keeping stopped, paused and parked work, history limits and device wiring refreshed before activation; AlertManager.rename and EventBus.rename/settle follow the names; flow and dashboard rename routes answer by code and repeat stored results; renamed, dashboard_changed and pipeline_rebuilt after release; fluksio serve reads flow files without building a FlowStore

2026-11-02 22:14:44 +01:00

artifacts.py

Camera permission and review fixes (openpanel C3, C4)

2026-10-17 09:20:04 +02:00

connector_store.py

Give connectors a store that survives restarts, and a way to clear it

2026-10-06 17:19:48 +02:00

connector_tls.py

Do not check a pinned certificate's dates

2026-10-07 10:11:08 +02:00

connector.py

connector: wanted(port) says whether anyone watches or reads a port

2026-10-27 15:20:24 +01:00

controller.py

Rename orchestration, splice and routes: a Renamer runs one rename at a time, closing the gate, taking the controller lock and holding the engine, each waiting without a limit and saying what it waits for (summary rename status, rename_waiting); DELETE on the pending request or a closed connection calls it off until the journal begins (409 aborted); then journal, steps and audit, retried in the background on failure (503 completing); splice_renamed rebuilds the affected flows under the held lock keeping stopped, paused and parked work, history limits and device wiring refreshed before activation; AlertManager.rename and EventBus.rename/settle follow the names; flow and dashboard rename routes answer by code and repeat stored results; renamed, dashboard_changed and pipeline_rebuilt after release; fluksio serve reads flow files without building a FlowStore

2026-11-02 22:14:44 +01:00

dashboards.py

Rename planner and document rewrite: rewrite_documents moves qualified names of the renamed flow in every flow (ports, inputs, outputs) and dashboard binding (one key table, WIDGET_BINDINGS, shared with the WidgetDef accessors, legacy pages included), published and draft, as plain JSON with both variants above either version; plan_rename reports documents, counts, fingerprint, warnings and refusals; superuser plan routes for flows and dashboards; key residue classifies state as the mapper does; duplicate retargets inputs and outputs too; queue reports its Redis version and other consumers

2026-11-02 21:06:39 +01:00

demand.py

connector: wanted(port) says whether anyone watches or reads a port

2026-10-27 15:20:24 +01:00

devices.py

History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

events.py

Rename orchestration, splice and routes: a Renamer runs one rename at a time, closing the gate, taking the controller lock and holding the engine, each waiting without a limit and saying what it waits for (summary rename status, rename_waiting); DELETE on the pending request or a closed connection calls it off until the journal begins (409 aborted); then journal, steps and audit, retried in the background on failure (503 completing); splice_renamed rebuilds the affected flows under the held lock keeping stopped, paused and parked work, history limits and device wiring refreshed before activation; AlertManager.rename and EventBus.rename/settle follow the names; flow and dashboard rename routes answer by code and repeat stored results; renamed, dashboard_changed and pipeline_rebuilt after release; fluksio serve reads flow files without building a FlowStore

2026-11-02 22:14:44 +01:00

executor.py

Engine holds for a rename: the pipeline refuses publish and inline cascades with EngineHeld once those running have finished, the execution service stops claiming and its timers once claimed cascades have finished; both wait without a limit, report what is busy and can be aborted. REST answers 503 with Retry-After, a device frame busy. Redis adds no longer wait for each other, only a queue hold waits for them

2026-11-02 20:21:17 +01:00

identity.py

Rename journal, steps and recovery: rename.json (RENAME_JOURNAL_FILE) records each step, documents are written whole and committed alone (FlowStore.replace_documents, identity.write_documents) and rolled back before the journal goes forward; history per run scoped by flow id, alert ledger, alerts.json, state and queue steps idempotent and checkpointed; audit row once per op; recover_documents before assign_ids and recover_runtime before the engine is built, retried until done; repeated requests get the stored result, stale ones 409; plan refuses rename_in_progress; alerts.json written atomically; completeness scanner in the test utilities

2026-11-02 21:30:01 +01:00

live.py

Camera permission and review fixes (openpanel C3, C4)

2026-10-17 09:20:04 +02:00

logs.py

Test hygiene: forget the refused study, quiet _Tee on a closed stream, wait for connector recovery

2026-10-14 23:41:31 +02:00

messages.py

Backend messages and field descriptions that reach the UI lose their em-dashes

2026-10-27 17:52:55 +01:00

metrics.py

History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

modules.py

Modules resolve the manifest with uv pip compile before syncing, so listed packages bring their dependencies

2026-10-15 17:06:20 +02:00

namespace.py

Startup deletes the work queue's keys from before it moved from pipeline: to queue: (stream, timers, dead letters, parked lists, done markers), logged with what they held; an old stream still holding undelivered work stays, is logged as an error, and counts as queued work for the keys it names

2026-11-03 07:55:14 +01:00

pipeline.py

Engine holds for a rename: the pipeline refuses publish and inline cascades with EngineHeld once those running have finished, the execution service stops claiming and its timers once claimed cascades have finished; both wait without a limit, report what is busy and can be aborted. REST answers 503 with Retry-After, a device frame busy. Redis adds no longer wait for each other, only a queue hold waits for them

2026-11-02 20:21:17 +01:00

placement.py

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

2026-10-28 08:07:35 +01:00

plugins.py

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

provision.py

A node's worker label is worker, so a device is only a paired one

2026-10-16 16:56:05 +02:00

queue.py

Startup deletes the work queue's keys from before it moved from pipeline: to queue: (stream, timers, dead letters, parked lists, done markers), logged with what they held; an old stream still holding undelivered work stays, is logged as an error, and counts as queued work for the keys it names

2026-11-03 07:55:14 +01:00

remote.py

Service node: a server kept running on a worker (openpanel V2)

2026-10-19 18:43:04 +02:00

rename.py

Rename orchestration, splice and routes: a Renamer runs one rename at a time, closing the gate, taking the controller lock and holding the engine, each waiting without a limit and saying what it waits for (summary rename status, rename_waiting); DELETE on the pending request or a closed connection calls it off until the journal begins (409 aborted); then journal, steps and audit, retried in the background on failure (503 completing); splice_renamed rebuilds the affected flows under the held lock keeping stopped, paused and parked work, history limits and device wiring refreshed before activation; AlertManager.rename and EventBus.rename/settle follow the names; flow and dashboard rename routes answer by code and repeat stored results; renamed, dashboard_changed and pipeline_rebuilt after release; fluksio serve reads flow files without building a FlowStore

2026-11-02 22:14:44 +01:00

resources.py

Backend messages and field descriptions that reach the UI lose their em-dashes

2026-10-27 17:52:55 +01:00

runs.py

Admission gate for a rename: RenameGate in flow/rename.py, installed by main.AdmissionGate inside CORS, turns mutating API requests away with 503 renaming and Retry-After while closed and drains those admitted without a limit, abortable; affected flows' hooks get 503 or socket close 1013, reads, sign-in, assistant, workers, artifacts and rename routes pass; the run cache misses while the gate is closed; trigger_node lets EngineHeld through instead of reporting a node failure

2026-11-02 20:53:08 +01:00

schemas.py

History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

secrets.py

Backend messages and field descriptions that reach the UI lose their em-dashes

2026-10-27 17:52:55 +01:00

state.py

Rename migrations for live state and the work queue: state keys move with RENAMENX in batches (type, TTL and history capacity kept), the queue rebuilds its streams with the same ids, group and pending entries, rewrites timers, parked and held items and done markers, and can hold new work in a list released in order; nothing calls them yet

2026-11-02 19:50:54 +01:00

store.py

Rename journal, steps and recovery: rename.json (RENAME_JOURNAL_FILE) records each step, documents are written whole and committed alone (FlowStore.replace_documents, identity.write_documents) and rolled back before the journal goes forward; history per run scoped by flow id, alert ledger, alerts.json, state and queue steps idempotent and checkpointed; audit row once per op; recover_documents before assign_ids and recover_runtime before the engine is built, retried until done; repeated requests get the stored result, stale ones 409; plan refuses rename_in_progress; alerts.json written atomically; completeness scanner in the test utilities

2026-11-02 21:30:01 +01:00

supervision.py

Make documentation standalone and generalize examples

2026-10-25 14:43:20 +01:00

telegram.py

Alerts: a Telegram channel, one chat or group each, connected by a one-time link

2026-10-28 13:06:58 +01:00

tombstones.py

History is kept by flow id: runs, cascades, rollups and events file the id in their flow column and nodes as <flow id>.<node>, the API answers flow plus flow_name and shows and takes nodes as <key>.<node>; events carry flow_id from the moment they are published; run queue items, the stage cache and cached curves keep ids and keys apart; endpoints, the brain graph, device bindings and search name the id to open

2026-11-02 19:01:19 +01:00

watchdog.py

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

webpush.py

Rename Installation to Instance

2026-08-31 10:12:01 +02:00

workers.py

Camera permission and review fixes (openpanel C3, C4)

2026-10-17 09:20:04 +02:00