Populate WorkerListInfo when returning ListWorkersResponse#9418
Merged
Populate WorkerListInfo when returning ListWorkersResponse#9418
Conversation
1 task
rkannan82
force-pushed
the
kannan/worker-summary-server
branch
4 times, most recently
from
05c048c to
00a7f7a
Compare
rkannan82
changed the title
rkannan82
changed the title
rkannan82
force-pushed
the
kannan/worker-summary-server
branch
4 times, most recently
from
9906c80 to
603e736
Compare
rkannan82
changed the title
rkannan82
force-pushed
the
kannan/worker-summary-server
branch
3 times, most recently
from
58311b5 to
400ae24
Compare
rkannan82
added a commit
to temporalio/api
that referenced
this pull request
Mar 10, 2026
## What changed? - Add `WorkerListInfo` proto for List API (follows CHASM entity conventions like `ActivityExecutionListInfo`, `ScheduleListEntry`) - Add `workers` field to `ListWorkersResponse` returning `repeated WorkerListInfo` - Deprecate `workers_info` field in `ListWorkersResponse` [Server PR](temporalio/temporal#9418) ## Why? Listing many workers with full `WorkerInfo` (containing dynamic metrics) is expensive. `WorkerListInfo` contains only static/slow-changing fields for efficient listing. ## How did you test it? - [x] make proto passes ## Potential risks None - backward compatible.
temporal-cicd bot
pushed a commit
to temporalio/api-go
that referenced
this pull request
Mar 10, 2026
## What changed? - Add `WorkerListInfo` proto for List API (follows CHASM entity conventions like `ActivityExecutionListInfo`, `ScheduleListEntry`) - Add `workers` field to `ListWorkersResponse` returning `repeated WorkerListInfo` - Deprecate `workers_info` field in `ListWorkersResponse` [Server PR](temporalio/temporal#9418) ## Why? Listing many workers with full `WorkerInfo` (containing dynamic metrics) is expensive. `WorkerListInfo` contains only static/slow-changing fields for efficient listing. ## How did you test it? - [x] make proto passes ## Potential risks None - backward compatible.
rkannan82
changed the title
- Add workerHeartbeatToListInfo helper in frontend to convert WorkerHeartbeat to WorkerListInfo for the new ListWorkersResponse.Workers field - Update tests to verify both deprecated WorkersInfo and new Workers fields The new WorkerListInfo proto contains only static/slow-changing worker info, enabling efficient listing of many workers without expensive dynamic data. Follows CHASM entity conventions (ActivityExecutionListInfo, ScheduleListEntry). - [x] built - [x] updated assertions in existing functional tests None - backward compatible. Deprecated WorkersInfo field continues to work. Made-with: Cursor
Update api-go to latest kannan/worker-summary-api (7ce2e200127a) which points to the squashed proto submodule. Add a test using proto reflection to verify all WorkerListInfo fields are populated by workerHeartbeatToListInfo. Made-with: Cursor
Made-with: Cursor
The api PR has been merged, so we can use the official module. Made-with: Cursor
Add Workers field to internal matchingservice.ListWorkersResponse proto so matching builds WorkerListInfo directly. Frontend now passes through resp.GetWorkers() instead of doing the transformation itself. Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
rkannan82
force-pushed
the
kannan/worker-summary-server
branch
from
0343853 to
c475173
Compare
birme
pushed a commit
to eyevinn-osaas/temporal
that referenced
this pull request
Mar 23, 2026
…o#9418) ## What changed? - Build `WorkerListInfo` in matching handler and pass through to frontend - Update `go.temporal.io/api` to include merged WorkerListInfo proto ## Why? `WorkerListInfo` contains only static worker attributes for efficient listing. Building it in matching (closer to the data source) enables eventually dropping the deprecated `WorkersInfo` field from the internal response. ## How did you test it? - [x] built - [x] added new unit test for field coverage - [x] covered by existing functional tests ## Potential risks None - backward compatible. Deprecated `WorkersInfo` field continues to be populated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
WorkerListInfoin matching handler and pass through to frontendgo.temporal.io/apito include merged WorkerListInfo protoWhy?
WorkerListInfocontains only static worker attributes for efficient listing. Building it in matching (closer to the data source) enables eventually dropping the deprecatedWorkersInfofield from the internal response.How did you test it?
Potential risks
None - backward compatible. Deprecated
WorkersInfofield continues to be populated.