VSCode pyre-check not linting, but CLI works fine about pyre-check

[sinancepel]

@Moxuz this looks like an unrelated issue where we weren't properly listening to VSCode's didSave requests, which I'm tracking at #20. I'll close this when a fix is rolled out for that.

[dkgi]

@sinancepel: can you take a look at this?

[sinancepel]

Hi @Moxuz, thanks for the report! This looks like VSCode isn't adding your virtual environment to your path. Could you try opening VSCode from your virtual environment in the terminal, and see if pyre works there?

As for the actual issue itself, I'll investigate whether we can automatically pick up on your virtual environment on the pyre-vscode side.

[chrispouliot]

Hey @sinancepel Thanks for the response. I have been using it/opening it from the virtual env in my terminal. I think the weird part is that it works once after a pyre restart but then stops after that.

The python version I am using in VSCode is also the pyenv virtualenv one, so that looks correct to me.

[sinancepel]

With the following commits, pyre should properly handle VSCode didSave requests, closing this issue. 0e41ed3 a245638