swarm-ui: let a closed stream reconnect and a failed caps read retry
When the server answers an event stream with an error status the browser gives up and the badge stayed on disconnected with nothing to press. The terminal, its state header and the messages page now offer a reconnect, and the one rule for the state after an error moved into a tested helper. The resource caps panel gets a retry beside its error, and its loading state announces itself.
This commit is contained in:
parent
9b1fe85706
commit
31b7452e56
9 changed files with 118 additions and 34 deletions
|
|
@ -59,6 +59,10 @@ dimmed, as **not running**.
|
|||
An agent's terminal opens with its last 100 rows from the past 24 hours, then
|
||||
follows new ones; a reconnect picks up after the last row it showed. A subagent
|
||||
terminal does the same with that subagent's rows, and has no turn-state badges.
|
||||
The browser retries a dropped connection by itself. When the swarm answers the
|
||||
stream with an error status, the browser gives up and the badge reads
|
||||
**disconnected**. The **reconnect** button beside it opens the stream again, and
|
||||
the stream replays the rows. The messages page works the same way.
|
||||
|
||||
The settings menu in the header has a **hide debug output** toggle. It drops
|
||||
the muted debug rows (thinking, coalesced ticks, harness chatter) from every
|
||||
|
|
@ -419,7 +423,8 @@ refusal's reason under the fields and leaves them as you typed them.
|
|||
A saved change isn't instant. The hive reads the caps about every 30 seconds,
|
||||
and a running agent takes a changed cap at its next spawn or rebuild, so the
|
||||
row shows the new value before the agent runs under it. The panel reads
|
||||
`GET /api/agents/{agent}/limits`. [hivectl](../tools/hivectl.md#per-agent-resource-limits)
|
||||
`GET /api/agents/{agent}/limits`; when that read fails, the panel shows the
|
||||
reason and a **retry** button. [hivectl](../tools/hivectl.md#per-agent-resource-limits)
|
||||
sets the hive's own limits.
|
||||
|
||||
### Settings at creation
|
||||
|
|
|
|||
Loading…
Reference in a new issue