what does it mean if (take! c f) calls f as expected if I haven’t started my app, but if I have started my app it only calls f if c already has data queued

does this mean that something is starving the put queue or the go threadpool?

(it’s likely there’s something bad going on in core.async world after a radical change to a lib, but I’m wondering how to look at and identify the specific problem, beyond looking very hard at the code until I see what is wrong)

the async threadpool being starved would be my guess

not starved, but blocked so the threads aren't able to process work

is there a good approach beyond guessing and reading jstack output?

if (clojure.core.async.impl.dispatch/run #(println "Hello World")) doesn't print

considering that everything is owned by the core.async threads so it can be hard to see where things are happening

yup, that must be it, it failed to print

so somebody is blocking all the go blocks, good to know

the core.async threads will be tagged with "async-dispatch-" when you look through jstack

OK - yeah, I found them, all blocking on the same code, thanks for the suggestions