Update to 2020.2 breaks remote codesniffer and mess-detector

Avatar
Permanently deleted user
Created

Since the update to PhpStorm 2020.2 codesniffer and mess-detector won't work anymore.

Here is the error message from the event log:

phpmd: bash: line 0: cd: [local_project_path]: No such file or directory 
Could not open input file: phpmd

[local_project_path] is the actual local project-path on my development machine which i have redacted.

Both, php itself and the quality tools, are set up for usage from a remote machine via ssh.

Any ideas on what to check? Or this a known bug?

Additional info: I'm running PhpStorm 2020.2 Build #PS-202.6397.115 on ArchLinux

Votes

0

Share

6 comments
Avatar
Eugene Morozov
Created

Tried to reproduce that (Windows 10 => Ubuntu over a remote interpreter), no luck, everything works.
Please try re-adding the remote interpreter and the Quality Tools configuration. Would that help?

0
Avatar
Permanently deleted user
Created

> Please try re-adding the remote interpreter and the Quality Tools configuration. Would that help?

Nope, no luck.

Let me add some more info:

  1. Now I know that I have two machines (one Windows 10, the other ArchLinux) which both show this behavior. Both connect to different but similar Ubuntu-Servers.
  2. The remote php-interpreter itself seems to work. It's only the quality-tools which generate these error messages in event log.
  3. The "Validate"-Buttons in the settings-windows work and detect the versions of the quality-tools no problem.

So: I'm kinda stumped what to try next… Anybody has any ideas?

0
Avatar
Permanently deleted user
Created

OK, I really don't know what else to do. I did the following steps and still got the same results:

  1. Created a new project => Same result
  2. Set up a new server-vm with an up-to-date Ubuntu Focal (and changed the ssh-config to allow password-login instead of key-authentication) => Same result
  3. Purged the complete .cache- and .config-folders of PhpStorm and created a new project (including new remote config of course) => Same result

I don't seem to get this working, no matter what I try. Any more advice?

0
Avatar
Eugene Morozov
Created

Just to prove that it works on my side: https://recordit.co/QCibAoX68x
Could you please record a similar screencast so that I maybe could spot some kind of misconfiguration?

0
Avatar
Permanently deleted user
Created

Hey Eugene,

thanks for your video. It helped me to repair my settings.

First difference is, that I use system-wide installed versions of phpmd and phpcs on the server. So the executables are located under /usr/bin.

With this prior to 2020.2 it was possible to just specify the names of the executables in the settings without the full path. This does not seem to be the case anymore. After I added the full paths everything works again.

I was just confused, because the "Validate"-Buttons also work without the full paths.

Again: Thanks for leading me in the right direction! Have a great week.

0
Avatar
Eugene Morozov
Created

Wow, thank you for the detailed description! It turned out that I processed a similar bug and couldn't even recall it. This is a bug, please vote: https://youtrack.jetbrains.com/issue/WI-53940

0

Please sign in to leave a comment.