app/backend/tests/api/routes at cb709c19ac4b230e80b94abd9940d0305045db80 - app

__init__.py

Vendor backend and frontend into the monorepo

2026-08-09 15:14:54 +02:00

test_alerts.py

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

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

test_camera_access.py

Make documentation standalone and generalize examples

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

test_cameras.py

Service node ends its call when the loop cancels every task; test order and timing leaks

2026-10-27 21:23:40 +01:00

test_code_rights.py

Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared

2026-11-02 17:41:23 +01:00

test_connectors.py

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

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

test_dashboards.py

Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared

2026-11-02 17:41:23 +01:00

test_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

test_docs.py

Enrol over http only to loopback; serve the API docs to this machine

2026-10-06 12:20:13 +02:00

test_flavors.py

Flows and dashboards are created by POST under an issued or superuser-pinned id; PUT only updates; deleted flows leave a tombstone with their key; the controller stores by id and runs by key, hooks live under /hooks/<flow id>; a key with state or queued work behind it is refused until cleared

2026-11-02 17:41:23 +01:00

test_flow_ids.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

test_flows.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

test_history_ids.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

test_live.py

Make documentation standalone and generalize examples

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

test_login.py

Bound what the API accepts, and close the holes the audit found

2026-08-29 20:40:05 +02:00

test_oauth.py

Serve MCP and hooks with a secret through the portal tunnel

2026-10-15 11:00:19 +02:00

test_observability.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

test_path_names.py

Flows and dashboards get ids: the store is addressed by id with a key index, the first start gives every document its key as id, fluksio store migrate --dry-run and ls; the rename routes are gone

2026-11-02 16:54:11 +01:00

test_private.py

Keep the engine's state in SQLite, not Postgres

2026-08-21 22:19:45 +02:00

test_runs.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

test_search.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

test_session.py

Rename the import package app to fluksio

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

test_socket_auth.py

Authenticate sockets by header or one-time ticket instead of ?token=

2026-10-07 08:58:22 +02:00

test_sync.py

Clients take a flow's id or key: one resolver in the SDK, id first, explicit id:/key:, a warning for reads and a refusal for changes when a name means two flows, deleted flows found by their last key; sync creates by POST, retries a create race through the drift checks and reports the id; MCP gets create_flow and resolves every flow argument with the caller's token; displays show flow_name; an engine from before ids is named as such

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

test_users.py

Count per-address limits on the hop a trusted proxy added; limit signup

2026-10-06 12:15:58 +02:00

test_workers.py

Workers screen shows each agent's version and protocol, and who is behind

2026-10-15 11:09:54 +02:00

test_wren_train.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