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

Drop the InfluxDB rotation item, note the orphaned flow state
Playwright Tests / test-playwright (1, 2) (push) Canceled after 0s
Details
Playwright Tests / test-playwright (2, 2) (push) Canceled after 0s
Details
pre-commit / pre-commit (push) Canceled after 0s
Details
Test Backend / test-backend (push) Canceled after 0s
Details
Compose Smoke Test / test-compose (push) Canceled after 0s
Details
Playwright Tests / merge-reports (push) Canceled after 0s
Details

Browse Source 
The token does not need rotating. Deleting a flow does leave its value,
timestamp, version and history keys behind in Redis.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkmeRiyeYmVZqJVwuyHq9o
This commit is contained in:
Melvin Strobl
2026-08-15 22:07:31 +02:00
co-authored by Claude Opus 5
parent 881d5c1cf2
commit 36be6f1081
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
NOTEPAD.md
+3 -4
View File
@@ -18,8 +18,10 @@ Deferring because out of scope is fine, but don't mention deferring than.
- CHORE/UI: `make test-backend` cannot reach Postgres while the integrated stack is up — - CHORE/UI: `make test-backend` cannot reach Postgres while the integrated stack is up —
`compose.local.yml` does `db: ports: !reset []`. Run it against the container's address, or `compose.local.yml` does `db: ports: !reset []`. Run it against the container's address, or
move the suite inside the compose network. move the suite inside the compose network.
- BUG/FLOW: deleting a flow leaves its state in Redis — the value, timestamp, version and
history keys under `pipeline:{flow}.*` all survive. Clear the namespace on delete.
- CHORE/UI: the Playwright specs run against the development stack and leave their users and - CHORE/UI: the Playwright specs run against the development stack and leave their users and
flows behind, which is why the flowbar fills with `test_flow_*`. Give them their own data flows behind, which is why the flowbar filled with `test_flow_*`. Give them their own data
or clean up after themselves, as `pytest` now does. or clean up after themselves, as `pytest` now does.
- CHORE/UI: the standalone Vite origin (`make dev-frontend` on :5173) is still not in - CHORE/UI: the standalone Vite origin (`make dev-frontend` on :5173) is still not in
`BACKEND_CORS_ORIGINS`. `scripts/setup.sh` regenerates the list on every `make init` and `BACKEND_CORS_ORIGINS`. `scripts/setup.sh` regenerates the list on every `make init` and
@@ -28,9 +30,6 @@ Deferring because out of scope is fine, but don't mention deferring than.
- CHORE/INFRA: `test-backend.yml` runs pytest on the runner host, so it keeps the fixed - CHORE/INFRA: `test-backend.yml` runs pytest on the runner host, so it keeps the fixed
container name and port 5432 that `compose.ci.yml` resets everywhere else. Two concurrent container name and port 5432 that `compose.ci.yml` resets everywhere else. Two concurrent
runs of that one job collide. runs of that one job collide.
- CHORE/FLOW: the InfluxDB token committed in the old `flow/nodes/influx_test.py` is in
pushed history (`d222ce5`). Rotate it in InfluxDB; removing it from history needs a
rewrite of published commits.
- PERF/UI: (deferred for now) the Monaco chunk is 2.6 MB. It only loads when a node panel opens, but the - PERF/UI: (deferred for now) the Monaco chunk is 2.6 MB. It only loads when a node panel opens, but the
editor could be trimmed further or swapped for CodeMirror if that becomes a problem. editor could be trimmed further or swapped for CodeMirror if that becomes a problem.
- CHORE/FLOW: `app/flow/nodes.py` is excluded from strict mypy (`[[tool.mypy.overrides]]` in - CHORE/FLOW: `app/flow/nodes.py` is excluded from strict mypy (`[[tool.mypy.overrides]]` in