redhat-developer / redhat-developer/abbenay
fix(grpc): GetConnectedWorkspaces should refresh via backchannel like REST
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 7
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
Summary
GET /api/workspaces in the REST API probes connected VS Code instances via a backchannel to get fresh workspace data before responding. The gRPC GetConnectedWorkspaces handler only returns cached getVSCodeWorkspaces() data without triggering a refresh.
This means gRPC clients may see stale workspace lists, especially if VS Code opened new folders since the last backchannel exchange.
Expected behavior
GetConnectedWorkspaces should trigger the same backchannel probe as the REST endpoint before returning results, or at minimum document that it returns cached data and provide a separate RefreshWorkspaces RPC.
Context
Identified during gRPC config parity audit in #32.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the REST GET /api/workspaces implementation and the gRPC GetConnectedWorkspaces handler, then trace how getVSCodeWorkspaces() and the backchannel probe are used. Done means gRPC clients receive refreshed workspace data like REST, or the cached-data behavior and separate RefreshWorkspaces RPC alternative are clearly resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100