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
This commit is contained in:
@@ -86,15 +86,28 @@ def test_train_submits_the_node_as_wren_s_installation(
|
||||
class Recorder:
|
||||
def submit(self, name, **kwargs):
|
||||
seen.update(kwargs, flow=name)
|
||||
return Run(id="train-1", flow=name, created_at=datetime.now(UTC))
|
||||
return Run(id="train-1", flow_id=name, created_at=datetime.now(UTC))
|
||||
|
||||
# Registered by sync, so under an id of its own: found by its key.
|
||||
registered = put_flow(
|
||||
client,
|
||||
superuser_token_headers,
|
||||
{"name": "wren_train", "mode": "batch"},
|
||||
"x_wren_train",
|
||||
)
|
||||
assert registered.is_success, registered.text
|
||||
monkeypatch.setattr(client.app.state, "run_service", Recorder())
|
||||
answer = client.post(f"{PREFIX}/control/train", headers=superuser_token_headers)
|
||||
try:
|
||||
answer = client.post(f"{PREFIX}/control/train", headers=superuser_token_headers)
|
||||
finally:
|
||||
client.delete(
|
||||
f"{settings.API_V1_STR}/flows/x_wren_train", headers=superuser_token_headers
|
||||
)
|
||||
|
||||
assert answer.status_code == 202, answer.text
|
||||
assert answer.json()["id"] == "train-1"
|
||||
assert (seen["flow"], seen["no_cache"], seen["cause"], seen["for_node"]) == (
|
||||
"wren_train",
|
||||
"x_wren_train",
|
||||
True,
|
||||
"train",
|
||||
f"{FLOW}.control",
|
||||
@@ -161,7 +174,7 @@ def test_a_node_reads_its_own_latest_training(
|
||||
session.add(
|
||||
Run(
|
||||
id=run_id,
|
||||
flow="wren_train",
|
||||
flow_id="wren_train",
|
||||
status="ok",
|
||||
for_node=f"{FLOW}.{node}",
|
||||
result={"exact_match": 0.98, "coverage": 0.9},
|
||||
|
||||
Reference in New Issue
Block a user