Open
Conversation
Implement CountWorkers RPC across frontend, matching, and worker registry. This provides a visibility API to count workers matching a query filter without retrieving full worker details. Changes: - Add CountWorkers to internal matchingservice proto - Implement CountWorkers in worker registry (reuses filterWorkers) - Wire through matching handler and frontend workflow handler - Add DC redirection, quotas, and genrpcwrappers routing - Add functional test for CountWorkers - Use replace directive for api-go with CountWorkers proto Made-with: Cursor
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
1 participant
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?
Add
CountWorkersRPC to count workers matching a query filter without retrieving full worker details.CountWorkersto internal matchingservice protoCountWorkersin worker registry, matching handler, and frontend handlerDepends on temporalio/api#729 (uses replace directive until merged).
Why?
The UI needs to display a worker count in places where listing isn't necessary. A dedicated count API follows the existing pattern (
CountWorkflowExecutions,CountSchedules).How did you test it?
Potential risks
None. New API only, no changes to existing behavior.
Made with Cursor