Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example for setting KeepAlive options in ConnectCallback on Linux #10866

Closed
bkindersleytrulioo opened this issue Jan 23, 2025 · 3 comments · Fixed by #10931
Closed

Example for setting KeepAlive options in ConnectCallback on Linux #10866

bkindersleytrulioo opened this issue Jan 23, 2025 · 3 comments · Fixed by #10931

Comments

@bkindersleytrulioo
Copy link

Describe the issue or suggestion

I can see that this snippet was added in response to this issue

however, it doesn't seem to work on a linux OS. based on this comment, that's expected behaviour, and a workaround is suggested, but it would be nice if there was an actual example with that workaround

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jan 23, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl

@MihaZupan
Copy link
Member

Sounds like a duplicate of dotnet/runtime#110124

@antonfirsov dotnet/runtime#111676 would fix this such that the workaround would no longer be required, right?

@antonfirsov
Copy link
Member

Yes, if we merge it .NET 10 will ship with the fix. On current versions unfortunately it's necessary to do the DNS resolution in the ConnectCallback.

Given .NET 8 end of support is in November 2026, I wonder if we should adjust the docs regardless?

@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants