Basically, what I want to look at right now is con...
# development
h
Basically, what I want to look at right now is console and browser reporting. We don't necessarily need zipkin per se, but it's all related. @aloof-angle-91616 it sounds like you're doing some stuff re console reporting, and I don't want to step on toes. Where are you at right now with that?
a
very basic, to service the use case of "pex is running a while, let's at least make sure the user knows it's not hanging by seeing progress output". it's currently hacked in by just manually teeing every stdout/stderr chunk from an
ExecuteProcessRequest
to the rust methods
std::io::std{out,err}()
which just allow you to write to the stdio streams with a big lock
i think console reporting in v2 (and in v1 too) can actually be really effectively decoupled from zipkin tracing, which is the opposite of what i thought previously