-
-
Notifications
You must be signed in to change notification settings - Fork 978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xdebug 3.3.1 and Blackfire PHP extension incompatibility #1118
Comments
Xdebug 3.3.2 was released yesterday. I tested it out, and it appears to fix this issue. I'll have a new build out shortly, so the |
markshust
added a commit
that referenced
this issue
Apr 16, 2024
markshust
added a commit
that referenced
this issue
Apr 16, 2024
markshust
added a commit
that referenced
this issue
Apr 16, 2024
markshust
added a commit
that referenced
this issue
Apr 16, 2024
Xdebug 3.3.1 and Blackfire PHP extension incompatibility #1118
markshust
added a commit
that referenced
this issue
Apr 16, 2024
Xdebug 3.3.1 and Blackfire PHP extension incompatibility #1118
This bug is now resolved. Awaiting the PHP image to be built before merging in #1123 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is currently an outstanding bug with Xdebug 3.3.1, which causes a 502 Gateway Error when it runs alongside the Blackfire PHP extension (see https://bugs.xdebug.org/view.php?id=2230).
Because of this, the PHP 8.1 and 8.2 images have been reverted to Xdebug 3.2.2. Since this version is incompatible with PHP 8.3, the Blackfire extension has been disabled by default in the PHP 8.3 image. This was patched and released in docker-magento 46.1.0.
If you wish to use Blackfire with PHP 8.3, please first disable Xdebug by running
bin/xdebug disable
, and then enable Blackfire withbin/blackfire enable
until this issue is resolved.Once the Xdebug but is resolved, we can upgrade Xdebug in all PHP images to that version, rebuild and retag the Docker images, and resolve this ticket.
The text was updated successfully, but these errors were encountered: