i.e. if I removed that and (eventually) replaced it with something making use of the python-side asynchronous workunit reporting I'm working on, would anyone complain?

we are planning on relying on it, yes... should check in with @average-vr-56795, @salmon-summer-38098, @dry-policeman-7927

legit, I'll avoid changing anything aobut how that code path works then

well, to be clear: it's ok to change things: just make sure you get some eyeballs on it before you do.

Yeah, best get @dry-policeman-7927's opinion, I think she did the heavy lifting on the zipkin stuff.

Happy for the code to be reframed so that a zipkin uploader uses the async reporting as some kind of registerable sink or similar, but we definitely want to be able to upload to zipkin

Well, yes, I don't think the proposal was to remove the functionality... 🙂

@happy-kitchen-89482: looking at the first comment in this thread, it sortof was, heh. but yea, agreement now