`reveal_type` does not work reliably about pyre-check HOT 3 CLOSED

Hi @cyounkins, thanks for the report.
I have been looking a bit into this.

I think that's because the pyre python client calls the pyre OCaml binary, and that one writes its logs to stdout, and then they go through multiple hops in the client: ocaml binary stderr -> log file -> tail -F -> pyre client stderr (i.e your terminal). My guess is that when we get the final result from the ocaml binary, the logs do not reach the final logger before we stop logging.
This happens around: https://github.com/facebook/pyre-check/blob/main/client/commands/analyze.py#L350-L361
Adding a time.sleep(1) there seems to fix the problem, but it is obviously less than ideal.
I think we need to increase the refresh rate of tail (using option -s), but that isn't available on MacOS, only on Linux. So we might have to implement our own tail function in Python (we discussed this before).

I have a fix internally, I will need to run more tests on it and go through code review.

from pyre-check.

So you were able to reproduce it then?

The reader could wait for a sentinel string. Or you could tail it yourself in python.

from pyre-check.

Yes I'm able to reproduce and I have a fix doing the tail in python. Please hold on while it goes through code review internally.

from pyre-check.