I always get thrown off by ruby, mainly because of rails magic though whenever I look at it. Convention over configuration hurts my brain some days. My only experience with testing there was rspec and cucumber. Wasn’t great at either of those, but loved pytest a lot

For testing I end up putting things in a docker container and running pytest through it for sanity checks. May have to update my testing approach soon though to cover more low-level validation. My memory error looks to be from closing a channel before a child goroutine could write to it. My working theory solution I’m trying out tomorrow is just wait for a second write to the channel from the other child routine before letting the function end. Seems a little hacky to me but it should hopefully work

It also had the added benefit of teaching me that goroutines will hold memory from fmt.Sprintf calls in cases where they were used only as a function argument in a logger.

Edit: removing a bad understanding of pprof on my part, I didn’t know until today that the allocs profiler shows lifetime data by default instead of inuse…

I ended up doing that. They said they would refund me when it got returned back to their warehouse when I talked to support.