-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[python/pyre.vim] Fix pyre persistent behavior #3895
[python/pyre.vim] Fix pyre persistent behavior #3895
Conversation
e0992b0
to
4380887
Compare
-l <project>
flag4380887
to
ac10c96
Compare
I'm seeing a couple of failures, but I'm not sure they're related to my change:
|
@oliverralbertini you changed the Revert the change or update the tests with the new value, whichever makes the linter work properly. |
Thanks @hsanson, great catch. I will just revert it, seems from the docs that it can be either a string of funcref:
|
It's necessary to provide a `-l` option to pyre with the closest parent directory containing a `.pyre_configuration.local` file, or simply change directory (cwd) to the root of the pyre project. Thanks to Ken Verbosky for the code that fixes this. Error seen when not using such a solution: ``` 1031.473923 on 6: Dropping message 'ƛ Background task unexpectedly quited: Invalid configuration: Cannot find any source files to analyze. Either `source_directories` or `targets` must be specified. ``` Issue with this approach is that if you are editing files under different projects, the `pyre persistent` process is not re-created for each file. We have to do `:ALEStopAlllsps` in order for the process to start with the new working directory.
ac10c96
to
3da3f3a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good.
It's necessary to provide a
-l
option to pyre with the closest parentdirectory containing a
.pyre_configuration.local
file, or simplychange directory (cwd) to the root of the pyre project. Thanks to Ken
Verbosky for the code that fixes this.
Error seen when not using such a solution:
Issue with this approach is that if you are editing files under
different projects, the
pyre persistent
process is not re-created foreach file. We have to do
:ALEStopAlllsps
in order for the process tostart with the new working directory.