XDebug | make all app | Mobile Application library

Ok, thanks to @waterloomatt I managed to find a workaround. The crux of the issue in my case is this PhpStorm bug: https://youtrack.jetbrains.com/issue/WI-54542 Therefore, this answer will probably be irrelevant once this bug is resolved.

Here's the solution on Linux :

In File->Settings->PHP->Servers, click on the "+" symbol to add a new server. Fill the server infos. The port is 63342, which is the port PhpStorm uses for running the code. Note that I gave this server the name "localhost63342". This detail is important.

Launch XAMPP as you do normally. The issue is with PhpStorm, not XAMPP.

Open a command prompt, and run the following command:

export PHP_IDE_CONFIG=serverName=localhost63342

Note the server name, which is the same as the name of the server we defined in PhpStorm.

I could make that environment variable more permanent, but since it is a soon-to-be-resolved PhpStorm bug, I think that'll do.

We defined an environment variable, which is valid as long as the command prompt remains open. We then can launch PhpStorm with this command prompt. In my case, with the following command:

./$HOME/phpstorm/PhpStorm-203.7148.74/bin/phpstorm.sh

My Chrome browser already has the "Xdebug helper" extension: https://chrome.google.com/webstore/detail/xdebug-helper/eadndfjplgieldjbigjakmdgkmoaaaoc?hl=en That extension is already configured to use the PHPSTORM IDE Key, as shown here:

In PhpStorm, I put a breakpoint where I want in my code. I click the button to make PhpStorm listen for PHP Debug Connections. I then launch the code from the page I want using the launcher button (Chrome is Alt+F2 on my computer).

The code runs normally, and I can navigate from page to page. When, on a specific page, the code hits a PHP breakpoints, the code is suspended, and I can execute it line by line using PhpStorm's debugger. Since I filled the forms to get to this page, I get the GET/POST data.

It's not as direct as a PHP HTTP Request I suppose, but it works.

I don't have a direct example, but I would approach this in the following way. The code is untested, and will likely require changes to work, take this as a starting point

In any case, you want to do the following things:

1. Collect code coverage data for each request, and store that to a file
2. Aggregate the code coverage data for each of these runs, and merge them

Collecting Code Coverage for Each Request

Traditionally code coverage is generated for unit tests, with PHPUnit. PHPUnit uses a separate library, PHP Code Coverage, to collect, merge and generate reports for the per-test collected coverage. You can use this library stand alone.

To collect the data, I would do composer require phpunit/php-code-coverage and then create an auto_prepend file, with something like the following in it:

XDEBUG_PATH_EXCLUDE is only used with xdebug_set_filter, which can filter out files for code coverage or stack traces only, and not for debugging.

Even if you could add it in an ini file (you can't), it wouldn't do anything.

I would recommend that you find out how to solve your original problem, "As we are having problems with our umask for PHP processes...", instead of coming up with a "hack" to change the umask with an auto prepend file.

Warning: Failed loading Zend extension 'xdebug.so' (tried: /usr/local/Cellar/php/8.0.6_1/lib/php/20200930/xdebug.so (dlopen(/usr/local/Cellar/php/8.0.6_1/lib/php/20200930/xdebug.so, 9): image not found), /usr/local/Cellar/php/8.0.6_1/lib/php/20200930/xdebug.so.so (dlopen(/usr/local/Cellar/php/8.0.6_1/lib/php/20200930/xdebug.so.so, 9): image not found)) in Unknown on line 0

Indicates that you're trying to load Xdebug twice. One time successfully so that it shows up in php -m, and one time with the wrong path, which gives this error. You need to find the wrong line in all of the ini files that are being loaded. You can find all the ini files that are being loaded with php --ini.

PHP on the CLI, and the PHP that runs through the web server might have different INI files. You can check which ones are used by using php --ini on the CLI, or using phpinfo() in a script that's run through the browser.

If they're using the same INI file, then check whether the value of xdebug.log is correct. Using php -m xdebug | grep log on the CLI, or again phpinfo() in a script.

If these are both correct, then it could also be a permissions issue. If the /path/to/xdebug.log has been created by the user that runs CLI commands (likely: you), then the webserver user will likely not have permissions to write to it too. You can check the owner and access rights of the log file with ls -l /path/to/xdebug.

It is also possible that the webserver user does not even have access to the /path/to part, which you can check with ls -l /path/to/, and verify whether the webserver user is part of the access mask.

If this is your personal machine (and not anything shared, or in production), you can fix the permissions on /path/to/xdebug.log with chmod 0666 /path/to/xdebug.log which should give all users write access to that file.

Turns out in the underlying code was calling an embedded Jetty server thus the actual pace where I needed the metrics from. Now to figure out how to get metrics from embedded jetty.

You're setting Xdebug 2 settings, but running Xdebug 3:

I'm sorry to say this but it looks like the problem is that you are using an unsupported PHP version. The broken mysqli::$stat property was removed in PHP 7.4. The solution is to upgrade your PHP version.

When triggering any MySQLi function the error and error properties are reset. You have to check it immediately after calling each function.

For example:

Basically, you should get the point (based on your latest comment). Docker is based on some command, when it's done - it stops the container.

So to make it continuously running you should have command and run infinitely.

Also check this answer as well, there are more explanation Why docker exiting with code 0

One of the easiest solution is to tail some logs. Like,