Jeff Allen

I'm 99% sure this fixes it for me. The 1% not sure comes from the fact that I have been unable to get a smoking gun A/B test to prove...

cc @mumbricht who is also suffering from this problem and would like a release to fix it.

I have a zopfli_test.go file that shows the problem and a fix for one of the cases.

Also, website/docs/intro/index.mdx has a broken link to /docs/plugin

Ok, definitely not a good plan to default to the first one, then. Let me try and figure out how I got the blank default. I recall just sort of...

Here's what happened. I started with no exoscale.toml file at all. I ran "exo compute instance list" and it reminded me to run "exo config" to get started. Ok so...

0775d98d51 fixes this by just throwing memory at it. Leaving this issue open because doing it right would be nicer.

I would expect that to happen when the TCP session is broken for some reason. Is it possible you are passing through a NAT which times out?

I am open to pull requests.

Hello @danielgtaylor . This is something we need at Exoscale, and we wanted to show it to you and see what you think. The fact that it pulls in code...