We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When we call the API to see what's the status of the MicroVM, the connection stays there and it's never closed (only when we restart the application).
Here is an isolated demonstration: https://github.com/yitsushi/firecracker-go-sdk-connection-leak-poc
Sample code:
func callAPI() { fcClient := client.NewHTTPClient(strfmt.NewFormats()) logger := logrus.NewEntry(logrus.New()) socketPath := "/tmp/firecracker.socket" transport := firecracker.NewUnixSocketTransport( socketPath, logger, true, ) fcClient.SetTransport(transport) resp, err := fcClient.Operations.DescribeInstance( operations.NewDescribeInstanceParams(), ) if err != nil { logrus.Error(err.Error()) return } logrus. WithField("state", *resp.Payload.State). Info("Firecracker API response") }
In the demo (link above) we are using github.com/firecracker-microvm/firecracker-go-sdk v0.22.0.
github.com/firecracker-microvm/firecracker-go-sdk v0.22.0
It's a very painful behavior because
References:
const MAX_CONNECTIONS
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When we call the API to see what's the status of the MicroVM, the connection stays there and it's never closed (only when we restart the application).
Here is an isolated demonstration: https://github.com/yitsushi/firecracker-go-sdk-connection-leak-poc
Sample code:
In the demo (link above) we are using
github.com/firecracker-microvm/firecracker-go-sdk v0.22.0
.It's a very painful behavior because
References:
const MAX_CONNECTIONS
): https://github.com/firecracker-microvm/micro-http/blob/36e59a083e76a2449e0f58e4283d201bc72fdf13/src/server.rs#L23The text was updated successfully, but these errors were encountered: