You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
I wish to silence all logging to the pyre.stderr file as I'm working in a repository where file modifications aren't possible. Since this does't seem to be an option I set the --log-level option to CRITICAL but successful runs still post the following message: 2024-09-12 03:34:30,643 [PID 1219] SUCCESS No type errors found
Reproduction steps
Run pyre --log-level=CRITICAL check
Expected behavior
If no errors that are set to the CRITICAL level are raised no messages should be posted to the stderr file.
Logs
pyre --log-level=CRITICAL check
Due to sensitive directories I am unable to post the output of pyre rage but I believe this is an easily reproducible issue. More generally I am curious if there are any combination of commands that can result in no file modifications while running pyre check.
The text was updated successfully, but these errors were encountered:
Pyre Bug: Unable to disable log generation
Bug description
I wish to silence all logging to the pyre.stderr file as I'm working in a repository where file modifications aren't possible. Since this does't seem to be an option I set the --log-level option to CRITICAL but successful runs still post the following message:
2024-09-12 03:34:30,643 [PID 1219] SUCCESS No type errors found
Reproduction steps
Run
pyre --log-level=CRITICAL check
Expected behavior
If no errors that are set to the CRITICAL level are raised no messages should be posted to the stderr file.
Logs
Due to sensitive directories I am unable to post the output of
pyre rage
but I believe this is an easily reproducible issue. More generally I am curious if there are any combination of commands that can result in no file modifications while runningpyre check
.The text was updated successfully, but these errors were encountered: