Closed adevade closed 2 weeks ago
@adevade oh, there seems to be an additional double quote in the coverage
command for the ini scan dir, which results in not correctly finding the php.ini file!
I fixed this in the next release.
In the meantime, you can manually apply a hotfix by changing line 95 in your herd.bat
file from:
-set "PHP_INI_SCAN_DIR="!PHP_BIN_DIR!!PHP_VERSION_NUMBER!"
+set "PHP_INI_SCAN_DIR=!PHP_BIN_DIR!!PHP_VERSION_NUMBER!"
This should be done in this file:
C:\Program Files\herd\resources\app.asar.unpacked\resources\bin\herd.bat
This file will be copied to your .config folder when restarting Herd.
@mpociot Can confirm it seems to work with the manual fix! 👍
Any tips or ideas of how to fix the Xdebug: [Step Debug] Time-out connecting to debugging client
console messages when using herd debug
?
This is now fixed with Herd 1.11.2
The timeout issue you mention comes from using herd debug without an active xdebug listener (like phpstorm)
@mpociot I'm happy to report that
herd debug
seems to work as expected after the update to v1.11.1 (aside from some xdebug timeouts in console). However,herd coverage
still isn't working for me... At least it seems to not be loading the SQLite extension. Seems to not be loading the default .ini at all.Here's some usage output to try to isolate the issue:
Here's
php --ini
for all commands: (Please note the leading double quote I mentioned previously on the path forherd coverage
. It's not present forherd debug
.)Sidenote: Both
debug
andcoverage
loads debug.ini as the main config, and then scans the additional folder for more files. Shouldn't all commands load the default .ini and the debug commands search for additional files?Originally posted by @adevade in https://github.com/beyondcode/herd-community/issues/1007#issuecomment-2393153170