sorry for the extended https://vore.website outage everyone!!
it started experiencing OOM issues immediately before i moved into a house, and i didn't find time/energy to fix it til now.
my commitment is to keep things running as best i can w/ the free time and energy i have available - in this case, the stars aligned wrong and it was down for a few weeks.
anywho, it's all patched up now!!
in the end, it was a silly http.Client timeout error. @forestjohnson has been warning me about these
@j3s classic golang infinite timeout by default right ? 🫠
yep 😭 here's the fix https://git.j3s.sh/vore/commit/402580307480a30b40be299f0b0d3581a88b06ef
(nevermind the context stuff, i was just throwing things at the wall)
i did discover a little bit about memory debugging while doing this tho: https://git.j3s.sh/vore/commit/e9ed53d5694105c7bc75ee9bfeca501cc4b1195b
that pattern will def come in handy. the pprof heap dumps were meaningless but the above helped me rule out certain feeds being huge/problematic
@j3s the context stuff should not be required afaik unless theres something in a library you use which requires a context passed to it.
Setting the timeout on the http client should be all you need.
Modifying the default http client is slightly frowned upon in programs that have dependencies and do a lot of stuff... But vore is simple enough its fine. Otherwise you can create your own http client and use that one instead of the default.
@j3s
https://git.sequentialread.com/sqr/greenhouse/src/branch/main/frontend.go#L107
```
sanityClient := &http.Client{
Timeout: time.Second * 20,
}
```
@forestjohnson gotcha, good to know!! i've heard many musings about the default http client, i suppose the alternative is to just make a unique one?