search

MLH-Fellowship / pyre-check

Performant type-checking for python.
https://pyre-check.org/
MIT License
3 stars 1 forks source link

Log issues to .pyre/pyre.stderr #90

Closed abishekvashok closed 1 year ago

abishekvashok commented 3 years ago

Pysa Feature Request

Hey, when running pyre analyze, have you guys considered logging the issues to stderr as well? For example, even when pyre runs in non-debug mode (without the -n option), it writes the debug mode output to .pyre/pyre.stderr but it just contains:

2021-11-19 10:45:13,851 [PID 26219] INFO Iteration #32. 0 Target []
2021-11-19 10:45:17,020 [PID 26219] INFO Found 5 issues
2021-11-19 10:45:17,021 [PID 26219] INFO Fixpoint iterations: 32
2021-11-19 10:45:17,021 [PID 26219] PERFORMANCE Analysis fixpoint complete: 797.49s
2021-11-19 10:45:17,193 [PID 26219] PERFORMANCE Analyze: 1802.36s

I guess we will get issues when we run with pyre -n analyze. To maintain similarity won't it be good to write the issues to pyre.stderr as well?

Is your feature request related to a problem? Please describe. No

Describe the solution you'd like Log the issue to .pyre/pyre.stderr

Additional context Is it because the client prints the results and not the server logging it? (I could be wrong here)