Coalesce the event bus, and fix the socket that ended on a client frame
A three-node cascade publishes 13-16 events and each one crossed to the
event loop on its own. They are one `call_soon_threadsafe` now — whatever
was published between two turns of the loop goes over together — and every
subscriber still receives every event, oldest still dropped first when one
falls behind.
The socket end of the same path:
- **any frame from the client ended its stream.** `receive_text` was
awaited once, outside the loop, so a keepalive — or anything else a
client decided to say — satisfied it and was read as the client going
away. It is recreated per iteration; only a disconnect ends the stream.
- events go out in one frame per wave (`{"type": "batch", "events": [...]}`,
capped at 64), serialised once with orjson rather than per client with
the stdlib's `json.dumps` through `send_json`. The client unpacks a batch
and still understands single frames, so an older engine behind a newer
bundle keeps working.
- authenticating and building the snapshot happen on a thread. Both were on
the event loop: one is a database round trip, the other reads the whole
of state, per connect and again per `dashboard_changed` per panel.
`Pipeline.values()` — what that snapshot is — no longer SCANs the whole
Redis namespace. It scanned five bookkeeping keys for every message to find
the messages; `RedisState` keeps a set of the names beside them and answers
from it. Maintained wherever a message is written, so a seeded value or a
deleted flow keeps it exact.
On the client, while in the same file:
- a `node_health` event invalidates the flow's detail. The canvas draws
health from the server-derived `issues`, so a node going down or
recovering only showed on mount, navigation or a rebuild. The store had
a health map of its own that nothing ever read; it and `useNodeHealth`
are gone rather than wired up, since the server's view is the one the
canvas already uses.
- a reconnect invalidates the five key families this socket feeds instead
of the entire cache, and the backoff is jittered. The usual reason a
socket dropped is the engine restarting, so every tab and every wall
panel refetched everything, together, at the moment it was least able to
answer.
- a frame that will not parse costs the frame, not the connection. It was
the one unguarded `JSON.parse` in the app; an exception there escaped to
`window.onerror` and left whatever it had already applied behind.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M6hPWS6YEbT1P8LxhhFb2T
This commit is contained in:
@@ -9,7 +9,7 @@ from __future__ import annotations
|
||||
|
||||
from abc import ABC, abstractmethod
|
||||
from collections import deque
|
||||
from collections.abc import Iterator
|
||||
from collections.abc import Iterable, Iterator
|
||||
from contextlib import contextmanager
|
||||
from threading import RLock
|
||||
from typing import Any, cast
|
||||
@@ -98,6 +98,15 @@ class StateBackend(ABC):
|
||||
"""Clear all keys in the state."""
|
||||
...
|
||||
|
||||
def message_names(self) -> list[str]:
|
||||
"""The message names in state, without the bookkeeping keys.
|
||||
|
||||
Its own method because the Redis backend can answer it from a set it
|
||||
maintains, rather than by scanning a namespace that holds five
|
||||
bookkeeping keys for every message.
|
||||
"""
|
||||
return [k for k in self.keys() if not k.startswith("__")]
|
||||
|
||||
def close(self) -> None: # noqa: B027
|
||||
"""Release whatever the backend holds outside this process.
|
||||
|
||||
@@ -510,18 +519,44 @@ class RedisState(StateBackend):
|
||||
data = cast(bytes | None, self._client.get(self._key(key)))
|
||||
return self._deserialize(data) if data is not None else default
|
||||
|
||||
def _names_key(self) -> str:
|
||||
return self._key("__names__")
|
||||
|
||||
def message_names(self) -> list[str]:
|
||||
"""The message names, from the set kept beside them.
|
||||
|
||||
`keys()` is a SCAN of the whole namespace, which holds a version, a
|
||||
timestamp, a history list and a last-seen marker for every message —
|
||||
so reading the message names cost several times as many round trips
|
||||
as there are messages. Every websocket connect asks for this.
|
||||
"""
|
||||
members = cast(set[bytes], self._client.smembers(self._names_key()))
|
||||
return [m.decode("utf-8") for m in members]
|
||||
|
||||
def _note(self, pipe: Any, keys: Iterable[str]) -> None:
|
||||
"""Record the message names among `keys`, in the caller's pipeline."""
|
||||
names = [k for k in keys if not k.startswith("__")]
|
||||
if names:
|
||||
pipe.sadd(self._names_key(), *names)
|
||||
|
||||
def set(self, key: str, value: Any) -> None:
|
||||
data = self._serialize(value)
|
||||
pipe = self._client.pipeline()
|
||||
if self._ttl:
|
||||
self._client.setex(self._key(key), self._ttl, data)
|
||||
pipe.setex(self._key(key), self._ttl, data)
|
||||
else:
|
||||
self._client.set(self._key(key), data)
|
||||
pipe.set(self._key(key), data)
|
||||
self._note(pipe, [key])
|
||||
pipe.execute()
|
||||
|
||||
def exists(self, key: str) -> bool:
|
||||
return bool(self._client.exists(self._key(key)))
|
||||
|
||||
def delete(self, key: str) -> None:
|
||||
self._client.delete(self._key(key), self._history_key(key))
|
||||
pipe = self._client.pipeline()
|
||||
pipe.delete(self._key(key), self._history_key(key))
|
||||
pipe.srem(self._names_key(), key)
|
||||
pipe.execute()
|
||||
|
||||
def clear(self) -> None:
|
||||
"""Clear all keys in the namespace."""
|
||||
@@ -568,6 +603,7 @@ class RedisState(StateBackend):
|
||||
pipe.setex(self._key(key), self._ttl, data)
|
||||
else:
|
||||
pipe.set(self._key(key), data)
|
||||
self._note(pipe, mapping)
|
||||
pipe.execute()
|
||||
|
||||
@contextmanager
|
||||
@@ -780,6 +816,7 @@ class RedisState(StateBackend):
|
||||
pipe.expire(history_key, self._ttl)
|
||||
for key in counters:
|
||||
pipe.incr(self._key(key))
|
||||
self._note(pipe, values)
|
||||
pipe.execute()
|
||||
|
||||
def history(self, key: str) -> list[tuple[float, float]]:
|
||||
|
||||
Reference in New Issue
Block a user