Open michealroberts opened 5 months ago
Hi Michael, Thank you for bringing up this issue. Looking at the problem that you stated which said that "Check command exited with non-zero return code: 126," generally indicates an issue with permissions or an inability to execute a binary. When I look at the issue that you are facing, i see some steps that can be taken to rectify the problem namely:
Check the executable permissions : As you are using a pyre in a container, there can be instances where the permissions can get mixed up. set the executable permission on the Pyre binary using "chmod +x /usr/src/app/.venv/bin/pyre.bin'
Based on the logs you provided, Pyre seems to ignore the "debug" flag set in the configuration file. You can enforce verbose output directly via the command line to get a little bit more details on the log. Try to modify the pyre command in the following way "poetry run pyre --noninteractive --debug check"
Try simplifying your .pyre-configuration temporarily to see if a particular configuration is causing the issue. Something like { "source_directories": ["."] }
Try running pyre outside of poetry to isolate the issue. source /usr/src/app/.venv/bin/activate pyre check
I beilieve that going through these debugging steps, you might be able to figure out the reason why you are facing the error in line 126. I hope this helps :)
Check command exited with non-zero return code: 126.
Bug description
When running
pyre check
which has been installed via poetry, withpoetry run pyre check
I am getting the following error code:Without any other debug information.
Reproduction steps
Simply pyre init inside a project, with watchman installed with the following configuration:
.pyre-configuraiton:
Expected behavior
It should run against the code, and exit safely.
Logs
pyre rage > pyre_rage.log
, Output:pyre_rage.log
Additional context
All I can say is I have a minimal python project inside a container, setup with poetry, and pyre and pysa do not work. Both exit with code 126 with no other output.
Is there a verbose mode where I can check further logs?