You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.
When working locally on a VM, the socket cannot be started, because of an exception being thrown whenever xdebug is enabled in the installation.
Exception trace:
1 trigger_error("XDebug extension detected. Remember to disable this if performance testing or going live!")
/vagrant/code/vendor/cboden/ratchet/src/Ratchet/App.php : 66
2 Ratchet\App::__construct("localhost", "8080", "127.0.0.1")
/vagrant/code/vendor/orchid/socket/src/Console/Server.php : 61
Please use the argument -v to see more details.
The text was updated successfully, but these errors were encountered:
The package does not work with the module enabled. Please disable it
Debugger always analyzes the script and stores it in memory,
since the socket does not die, this results in an endless memory devouring.
Is there a purpose for this not working with xdebug? This seems a bit arbitrary, especially since the exception message explicitly states that xdebug should be disabled in live, or performance testing environments. I am not in either of those environments, so I do not see why this does not work. Is there something in the source base that makes it incapable of running with xdebug outside of this exception?
When working locally on a VM, the socket cannot be started, because of an exception being thrown whenever xdebug is enabled in the installation.
The text was updated successfully, but these errors were encountered: