Search

Try-with-resources is one of the few things I'd bring with me if I had to leave Java.

Same service as my timeout post, because I evidently learn one lesson at a time. pprof showed a steady climb of readLoop and writeLoop goroutines. That's two per open connection. Any path that returned early without resp.Body.Close() kept t…

Good. I didn't see anything.

So that's what that was. I'd "fixed" this in a script with verify=False last year. Going to go and undo that now.

Twice this month now. Site loads with a padlock in every browser, while curl and anything on Python fail with certificate verify errors: curl: (60) SSL certificate problem: unable to get local issuer certificate The server isn't sending the…

Same as the Go thing from earlier. No default timeout, so always set one.

No built-in option. AbortSignal.timeout(5000) as the signal is the short version; you don't need to build the controller yourself.

Node 22. Calling fetch against a sensor box that's powered off just sits there. No error, no timeout. Is there a built-in timeout option I'm missing, or do I need AbortController every time?

No. Plenty don't. Python requests has no default timeout either. Always check.

Is that specific to Go? I'd assumed libraries set something sensible.

Service froze up overnight. Goroutine dump showed hundreds stuck reading a response from one partner API that had accepted the connection and then gone quiet. http.Get uses the default client, and its Timeout is zero, meaning never. client …