Skip to content

fix: disable idle mode on in-process loopback connection#66

Merged
talos-bot merged 1 commit into
siderolabs:mainfrom
utkuozdemir:fix/disable-grpc-idle-on-loopback-conn
Jun 20, 2026
Merged

fix: disable idle mode on in-process loopback connection#66
talos-bot merged 1 commit into
siderolabs:mainfrom
utkuozdemir:fix/disable-grpc-idle-on-loopback-conn

Conversation

@utkuozdemir

Copy link
Copy Markdown
Member

The local backend talks to the in-process apid server over an in-memory loopback transport, which has no use for gRPC idle mode since there is nothing to reclaim by going idle. This mirrors the same change made in Omni in siderolabs/omni#3011, and also bypasses a gRPC bug that can leave an idling connection permanently stuck.

The local backend talks to the in-process apid server over an in-memory loopback transport, which has no use for gRPC idle mode since there is nothing to reclaim by going idle. This mirrors the same change made in Omni in siderolabs/omni#3011, and also bypasses a gRPC bug that can leave an idling connection permanently stuck.

Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
@utkuozdemir utkuozdemir self-assigned this Jun 19, 2026
@github-project-automation github-project-automation Bot moved this to To Do in Planning Jun 19, 2026
@talos-bot talos-bot moved this from To Do to In Review in Planning Jun 19, 2026
@github-project-automation github-project-automation Bot moved this from In Review to Approved in Planning Jun 20, 2026
@utkuozdemir

Copy link
Copy Markdown
Member Author

/m

@talos-bot talos-bot merged commit f101d1f into siderolabs:main Jun 20, 2026
14 checks passed
@github-project-automation github-project-automation Bot moved this from Approved to Done in Planning Jun 20, 2026
@utkuozdemir utkuozdemir deleted the fix/disable-grpc-idle-on-loopback-conn branch June 20, 2026 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants