Error with PHP Code Sniffer and PhpStorm - phpstorm

17:18 PHP Code Sniffer
No response from /home/my_user/.composer/vendor/squizlabs/php_codesniffer/bin/phpcs after 5000 ms
Disable inspection
Any idea? I've tried a lot of solutions like disable xdebug, increment response time.
It does not work in PhpStorm but works in the terminal.

I looked into this problem today and it is caused by a change to the STDIN processing code for PHPCS 3.2.0. I don't know exactly why it looks like STDIN has content but nothing is coming through, but that's what PHPCS sees and so it waits forever. PHPStorm times out after 5 seconds (I think it is, by default).
I've pushed up a change to PHPCS to enforce a short time-out on STDIN and tested this change with PHPStorm, which is now working for me.
If you can use the current master branch for PHPCS, it should work ok. If not, reverting back to 3.1.1 (or earlier) is all you can do until 3.2.1 is released. I'm not sure when that will be just yet.

Related

PhpStorm not detecting file changes until focussing on another app

Been running into some issues with PhpStorm (v2020.3 on MacOS Big Sur 11.1) lately.
If I make changes to a file and save them, it doesn't trigger actions like a file transfer or recompiling (S)CSS when running npm run watch.
As soon as I focus another application (e.g. the browser for previewing) it detects the changed file and runs the needed action. This causes an annoying delay in my workflow.
At first I thought it had to do with Docker not updating the files in the container, however I now figured out it also does not work with a simple automated (s)FTP file upload/deplyoment.
Anyone else experiencing the same issue?
Cheers,
Allard
Fixed it by remapping the Save document shortcut under Preferences > Keymap. No idea how the shortcut got messed up, but hey, it works.

PhpStorm showing "unvailable" breakpoint whereas execution is suspended

I'm sometimes stuck while attempting to debug my code.
Debug Session is active, code execution is suspended :
But I cannot see what really happens, as the breakpoint show "unavailable" ("no parking" symbol):
Does anybody know about this sign ?
I still haven't found any information about it on JetBrains sites... that's why I'm here :-)
(PhpStorm 2020.3, using docker containers (linux containers) with Docker Desktop/ Windows 10)
[EDIT] :
I just noticed that "break at first line in php script" seem to be functioning though:
But I have these weird breakpoints instead of red "normal" ones, and an highlighted line.
I tried restarting my docker containers, same issue. This produces seemingly randomly and gets solved after a while ... (reboot ?...)
[EDIT] SOLVED
The path mapping (local<->docker) for the root of my project was empty (how did it happen...) in my docker configuration in PhPStorm.
I'm not sure how this problem occured, but I'll be able to solve it next time if it's back.
If you try to disable "break at first line in php scripts" you may get the message :
17:38 Debug session was finished without being paused It may be
caused by path mappings misconfiguration or not synchronized local and
remote projects. To figure out the problem check path mappings
configuration for 'docker-server' server at PHP|Servers or enable
Break at first line in PHP scripts option (from Run menu). Do not
show again
In my case, the path mapping for the root of my project was incomplete "Absolute path on the server" was emtpy. I don't know how it happened but you could check :
In PHP | Servers

Xdebug stops on xdebug_break() but not on breakpoints in PhpStorm during PHPUnit run

I used to be able to stop on break points during my PHPUnit runs, but a recent PhpStorm update has messed that up. I am able to use xdebug_break() but not an IDE break point.
Anyone else had that issue?
I got it working by fixing my config.
Go to: Preferences->Languages & Frameworks->PHP->Servers
Make sure the 'Absolute path on server' correctly correlates to your project.
Mine was blank so I had to set it.

Google chrome failed to parse extension manifest

After upgrading Google chrome from 34 version to 35 it doesn't work.
I use debian testing. As soon as I run
google-chrome
from console I get an error:
"Error...: failed to parse extension manifest" after that I get login screen.
I've tried to reinstall the browser, cleaned chrome's cache and config folders. But result the same.
Also I can't get detail log. I tried to run google chrome from console like:
google-chrome > log.txt
but I got empty log.txt file.
Also I checked /var/log/... files. But I didn't find anything interesting.
It would be great if someone tells me how I can get detailed log information or how to fix this issue:)
Try
chrome 2> log.txt
Same here. But I not even get to any screen. Crashes right away after an update (there was a new Chromium AND also kernel update coming following each other a few days apart. Because I didn't start Chromium in between I cannot even tell what could cause this.
I also assume that ""Error...: failed to parse extension manifest"" here is a side effect of something more severe. I get more errors like:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[7351:7351:0614/212426:ERROR:sandbox_linux.cc(297)] InitializeSandbox() called with multiple threads in process gpu-process

Jenkins/Hudson fails when trying to retrieve code from CVS

Trying to configure Jenkins CI. Currently just running it from the .war (eventual intention as a service). Jenkins is aware of the CVS executable (i.e. will read the version [Concurrent Versions System (CVSNT) 2.0.62.1817 (client/server)]).
The .cvspass is not specified, because they apparently do not play nice with CVSNT (which prefers to keep passwords in the registry.) I've specified the password in the job config by using the :pserver:user:passg#server:/dir pattern for CVSROOT, which I found suggested in some places. Regardless of whether I run using that, or :pserver:userg#server:/dir as the CVSROOT I get the blinking red ball, jenkins stuck with a nearly full progress bar for 2 and a half minutes. It then fails. The console output yells with something like
FATAL: hudson.scm.ChangeLogSet.iterator()Ljava/util/Iterator;
java.lang.AbstractMethodError: hudson.scm.ChangeLogSet.iterator()Ljava/util/Iterator;
at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:282)
at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:279)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:596)
at hudson.model.Run.run(Run.java:1400)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:175)
Both CVSROOTs I'm using provide no trouble with TortoiseSVN. I've found some mention of difficult of logging into SVN from jenkins as a service and related user/system issues, but considering I'm running it from the .war I don't think that's the issue.
EDIT:
Interestingly the console log if I use an invalid user or password recognizes such.
cvs [checkout aborted]: authorization failed: server rejected access to /dir for user FOO
FATAL: CVS failed. exit code=1
Finished: FAILURE
which indicates that Hudson is talking to the CVS server and authenticating, but something else goes wrong.
/EDIT
Cheers
Answer to the question found, thanks to rpetti on #jenkins on freenode. Problem was I had switched between Hudson and Jenkins and there were some incompatible configuration files that were mucking things up. Deleting and recreating the home directory solved the problem.
CVSNT 2.0.62.1817 is very very old and has several known security issues. Please upgrade to the latest 2.8.01.