Skip to content

fix(ui): show when the Substrate lists were read, not a running age - #3545

Merged
Charlesthebird merged 2 commits into
kagent-dev:mainfrom
Charlesthebird:charlesthebird/substrateReadAt
Nov 6, 2026
Merged

Charlesthebird merged 2 commits into
kagent-dev:mainfrom
Charlesthebird:charlesthebird/substrateReadAt

Conversation

@Charlesthebird

@Charlesthebird Charlesthebird commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Written by 🤖 (start)

The Substrate page's actor and worker lists now show Read at 4:41:02 PM instead of read 12.3s ago, which re-rendered twice a second and pulled the eye off the rows. While polling, a list that goes 3 intervals (at least 5s) without a new read adds its age in the warning colour, e.g. Read at 4:41:02 PM, 12s ago.

Testing

  1. Open Substrate. Each list shows Read at <time>, which changes only when the list refreshes.
  2. Turn polling on, then make the API hang. After about 5s, each list reads Read at <time>, <n>s ago in amber.

Written by 🤖 (end)

The actor and worker lists read "read 12.3s ago" and re-rendered twice a
second, which pulled the eye off the rows. They now read "Read at
4:41:02 PM", which changes only when the list refreshes.

Signed-off-by: Nicholas Bucher <[email protected]>
@github-actions github-actions Bot added the bug Something isn't working label Nov 5, 2026
"Read at 4:41:02 PM" stays still while polling stalls, so a list that
stopped updating looked the same as a fresh one. Once a polled list goes
3 intervals, and at least 5s, without a new read, it now reads "Read at
4:41:02 PM, 12s ago" in the warning colour. The age is measured on the
browser's clock from the last new read, so server clock skew cannot
raise it.

Signed-off-by: Nicholas Bucher <[email protected]>
@github-actions github-actions Bot added bug Something isn't working and removed bug Something isn't working labels Nov 5, 2026
@Charlesthebird

Charlesthebird commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator Author

Recorded on a local kind cluster running kagent with Substrate, main against this branch.

  • Substrate actor and worker lists: read 9.0s ago ticked twice a second; both now read Read at 5:30:52 PM and stay still.
substrate-read-time.mp4

Screenshots

Before: Substrate lists before-substrate-read-time
After: Substrate lists after-substrate-read-time

Written by 🤖

@Charlesthebird

Charlesthebird commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator Author

Degraded states on this branch, same kind cluster, dark mode.

  • Reads hanging: with polling on and the controller connection paused, both lists turn amber and read Read at 5:34:10 PM, 10s ago; reads slower than this rate shows beside the interval.
  • Read failing: with the controller unreachable, each section shows its error banner (HTTP 502).

Screenshots

Substrate: reads hanging, polling on

state-substrate-reads-hanging

Substrate: a read failing

state-substrate-read-failing

Written by 🤖

@Charlesthebird
Charlesthebird marked this pull request as ready for review November 5, 2026 22:58
@EItanya
EItanya added this pull request to the merge queue Nov 6, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 6, 2026
@Charlesthebird
Charlesthebird added this pull request to the merge queue Nov 6, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 6, 2026
@Charlesthebird
Charlesthebird added this pull request to the merge queue Nov 6, 2026
Merged via the queue into kagent-dev:main with commit 7c9c521 Nov 6, 2026
56 of 57 checks passed
@Charlesthebird
Charlesthebird deleted the charlesthebird/substrateReadAt branch November 6, 2026 20:08
jerry-jibu pushed a commit to jerry-jibu/kagent that referenced this pull request Nov 14, 2026
Backports seven PRs from `main` to `release/v1.0.x` for the 1.0 release.
Each is cherry-picked with `-x` in its original merge order, and none
needed changes. Every file these commits touch now matches `main`
exactly.

| PR | Commit | Why |
| --- | --- | --- |
| kagent-dev#3558 | `2e2acf58c` | fix(ci): restore upgrade tests from RC3 |
| kagent-dev#3545 | `7c9c52105` | fix(ui): show when the Substrate lists were
read, not a running age |
| kagent-dev#3395 | `aaf1ca882` | feat(session): revert crashed runtimes through
RevertSession (needed for a customer) |
| kagent-dev#3562 | `5c490d83b` | refactor: remove helpers orphaned by the KMCP
removal (low risk; keeps the branch close to `main`) |
| kagent-dev#3563 | `c6adf72f9` | refactor(api): move MCP header resolution out of
`v1alpha3`, so the 1.0 API package describes only data |
| kagent-dev#3340 | `347acbe55` | fix(controller): move a ModelConfig condition's
transition time only on a status change (labeled `cherrpick-1.0`) |
| kagent-dev#3560 | `ccb2dd350` | adk/mcp: defer tool discovery until invocation,
so slow MCP discovery no longer fails agent resumes |

Please use **Rebase and merge** so each backported PR stays its own
commit on the release branch.

Validation before kagent-dev#3560 was added (CI covers the full set):
- `go build ./...` and `go vet ./...`
- `go test -race` with envtest for `api`, `core/cli`,
`core/internal/{controller,database,grpcserver,mcp,service,substrate}`,
`core/pkg/migrations`, and `pkg/logging`
- `make -C go lint`: 0 issues
- UI `tsc --noEmit` and `substrateReadAge.test.tsx`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Signed-off-by: Eitan Yarmush <[email protected]>
Signed-off-by: Nicholas Bucher <[email protected]>
Signed-off-by: Ada Lundhe <[email protected]>
Signed-off-by: timflannagan <[email protected]>
Signed-off-by: QuentinBisson <[email protected]>
Signed-off-by: Shashank Ram <[email protected]>
Co-authored-by: Nicholas Bucher <[email protected]>
Co-authored-by: Ada Lündhé <[email protected]>
Co-authored-by: Claude Opus 5.5 <[email protected]>
Co-authored-by: Tim Flannagan <[email protected]>
Co-authored-by: Quentin Bisson <[email protected]>
Co-authored-by: Shashank <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants