![]() ![]() ![]() Why WSL has a part on it? it can easily be explained by this stack overflow post: Like what I have said, these issues are compounded with the fact that WSL is being used.I cannot confirm which version I was using at the moment as I do not have that machine with me right now. However, I tried this env var on a very fresh installation of Laravel the night I last commented and can confirm that SAIL_XDEBUG_MODE does work on that setup. I am 100% on this as I dragged it over the coals but it was on version ^1.13. the env var SAIL_XDEBUG_MODE does not work on specific versions of laravel/sail.There are actually two things in play here: I was actually able to make it 100% work but I just snoozed over this PR when I figured out everything the night I last commented, even issue. If I do get some luck, I'm happy to pour in doco for Hey mate, apologies if this is 4 weeks late and I appreciate the effort. The internet also isn't helping as nobody seems to have fully demonstrated a working WSL + Docker + PHP/Xdebug 3 setup working yet, at least for my case. I'm still not overly successful with using Xdebug here, but I don't blame Laravel for it as my issues right now seem to be wildly about Docker. I saw your PR, and based on this information, it seems that it did not need that many changes, because simple adding the key/value into any value in php.ini will be enough for it to be overriden by XDEBUG_MODE. ![]() Maybe it's worth checking in Xdebug 3 issue tracker for this? Then when you set XDEBUG_MODE, it will override the master value as a local value, over any declaration made on XDEBUG_CONFIG. It doesn't have to be the value you want, it only needs to exist. I agree that the documentation should be much more clearer about this, but I also think that there is something amiss about Xdebug 3's documentation as it doesn't seem to allow you to override it via environment variables.Īfter a few tests, I observed that overrides in XDEBUG_MODE only works if you define the master value first by declaring it in the. You might want to keep this open as it is still an outstanding issue.
0 Comments
Leave a Reply. |