Skip to content

Conversation

@Nino-K
Copy link
Contributor

@Nino-K Nino-K commented Jan 11, 2023

Currently, we are leaving the response writer open for both connected sockets (TCP) and non-connected sockets (UPD), this change closes the response writer accordingly.

This change is meant to address the user-reported issue on Lima: #1285

Signed-off-by: Nino Kodabande nkodabande@suse.com

Currently we are leaving the response writer open for both
connected sockets (TCP) and non-connected sockets (UPD),
this change closes the response writer accordingly.

Signed-off-by: Nino Kodabande <nkodabande@suse.com>
@jandubois jandubois added this to the v0.15 (tentative) milestone Jan 11, 2023
@jandubois jandubois linked an issue Jan 11, 2023 that may be closed by this pull request
Copy link
Member

@jandubois jandubois left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Copy link
Member

@AkihiroSuda AkihiroSuda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@AkihiroSuda AkihiroSuda merged commit f26b412 into lima-vm:master Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Lima get stuck when certain frequency of DNS resolution occurs

3 participants