Artifact 0b83e4a6326dddc8c7eb8970140893ad6eea22a152d0a7b5f2393efaa9ac5964:
- File
internal/web/web_test.go
-
2026-08-26 12:43:53
— part of check-in
[0f1c202c58]
on branch tl-rev
— Timeline: a revision signal, not rendered rows
The stream carried the filter it was opened with, so every later tick repainted the reader's page with a view they had left. That is not a bug that gets fixed once — it shipped, was fixed this morning, and would come back the next time a default moved, because the shape makes it possible.
The fleet page was rebuilt around a revision number for this reason. The timeline now follows: the signal says THAT the repository changed, the client re-requests the listing and sends its own controls with it. Nothing can capture a filter and outlive it.
A fragment is delivered as SSE but is a render, so it is marked and still measured — otherwise the refresh path would have been the one route the ops panel could not see. (user: dmestas, size: 80543) [annotate] [blame] [check-ins using]
- 2026-08-26 12:44:12 — part of check-in [105cfb9c18] on branch trunk — Accepted. A revision cannot go stale; a rendered row can. (user: dmestas, size: 80543) [annotate] [blame] [check-ins using]
-
2026-08-26 12:43:53
— part of check-in
[0f1c202c58]
on branch tl-rev
— Timeline: a revision signal, not rendered rows