Skip to content

Closes the responseWriter after serving the Answer #1294

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

Merged
merged 1 commit into from
Jan 11, 2023

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 [email protected]

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 <[email protected]>
@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