/cache is not successful at warming the cache

[kingdonb]

/cache is not successful at warming the cache

[kingdonb]

From:

• #345

It's great! And it's an example of ruby fibers for concurrency (I needed for my process to wait around 4 hours between pulling the current set of promises and whether they've been finished yet so I started with a script that exits when it's done, calls sleep for 4 hours, and then executes itself again after the wait... but that was clunky and difficult to monitor and test, so I decided to implement fibers with an "hourly heartbeat" to see if the fiber scheduler is still working and a 4-hourly scrape.)

So to the point... I have this other process, which is related to commits.to and has an hourly job

I think rather than using CronJob resources, which are going to use Kubernetes Job we can keep the design simpler (I don't currently manage 1 or more Kubernetes CronJob resources, so it's simpler not to add one then...) by leveraging this process that exists which already has an hourly heartbeat! Just making a note of this here before I forget that connection.

The other half of this problem is just firing up a debugger, and ensuring that we can actually hit the /cache endpoint without crashing the request. I had a stack dump but I don't have it handy at this moment.