-
Notifications
You must be signed in to change notification settings - Fork 260
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
[PHP.wasm] Missing mysqli_report function #1990
Comments
Thank you for reporting this error @burncrete! I adjusted the title to match your error, but I don't fully understand what caused it from reading the error log. Could you please share some instructions on how to recreate this issue, or ideally a Blueprint that causes the error? |
I too am uncertain of how the error occurred. hereafter, navigating to plugin Tab, to activate Query Monitor plugin. then critical error triggered. |
@burncrete, was this with a saved site, and if so, do you know if the site was saved to the browser or to the local directory? This is an interesting error. The only place I see It seems like the sqlite-database-integration DB override would have to be skipped for this error to occur. |
Were there any other interesting details of the configuration in this case, besides changing the selected PHP version? |
I can recreate this by installing Query monitor: https://playground.wordpress.net/?plugin=query-monitor |
We could add an empty function like we did with mysqli_connect. |
Nonother notable errors. besides that instance |
What was the Blueprint you used @burncrete? The mysqli_report call that triggered this error is used in the WPDB class. That code path should never run in Playground – the SQLite integration plugin ships its own WPDB implementation with no Seeing a |
there are saved playgrounds. namely funny vintage park & loyal cozy village |
Debug logs loyal cozy village.txt |
@burncrete thank you for that detail! Would you mind sharing the original Blueprint used to create them? You can view it here: |
Please see attached.
Whether or not this would be helpful, as previously stated the playground loaded perfectly fine. Until attempting to activate Query monitor which crashed the site.
…________________________________
From: Adam Zieliński ***@***.***>
Sent: Wednesday, November 13, 2024 4:36 PM
To: WordPress/wordpress-playground ***@***.***>
Cc: Justin Dearling ***@***.***>; Mention ***@***.***>
Subject: Re: [WordPress/wordpress-playground] [PHP.wasm] Missing mysqli_report function (Issue #1990)
@burncrete<https://github.com/burncrete> thank you for that detail! Would you mind sharing the original Blueprint used to create them? You can view it here:
***@***.*** (view on web)<https://github.com/user-attachments/assets/0427e9b9-9dbe-45cb-b51a-1e4809680d9a>
—
Reply to this email directly, view it on GitHub<#1990 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIAYUH2ODM7QZML2BXVDXV32ANPXFAVCNFSM6AAAAABRNLOAAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZTHAYDAOJVG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
|
________________________________
From: Justin Dearling ***@***.***>
Sent: Thursday, November 14, 2024 9:46 AM
To: WordPress/wordpress-playground ***@***.***>
Subject: Re: [WordPress/wordpress-playground] [PHP.wasm] Missing mysqli_report function (Issue #1990)
Please see attached.
Whether or not this would be helpful, as previously stated the playground loaded perfectly fine. Until attempting to activate Query monitor which crashed the site.
…________________________________
From: Adam Zieliński ***@***.***>
Sent: Wednesday, November 13, 2024 4:36 PM
To: WordPress/wordpress-playground ***@***.***>
Cc: Justin Dearling ***@***.***>; Mention ***@***.***>
Subject: Re: [WordPress/wordpress-playground] [PHP.wasm] Missing mysqli_report function (Issue #1990)
@burncrete<https://github.com/burncrete> thank you for that detail! Would you mind sharing the original Blueprint used to create them? You can view it here:
***@***.*** (view on web)<https://github.com/user-attachments/assets/0427e9b9-9dbe-45cb-b51a-1e4809680d9a>
—
Reply to this email directly, view it on GitHub<#1990 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIAYUH2ODM7QZML2BXVDXV32ANPXFAVCNFSM6AAAAABRNLOAAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZTHAYDAOJVG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
[14-Nov-2024 07:48:28 UTC] JavaScript Error: PHP.run() failed with exit code 255 and the following output: PHP Fatal error: Uncaught Error: Call to undefined function mysqli_report() in /wordpress/wp-includes/class-wpdb.php:3
Stack trace:
#0 /wordpress/wp-includes/class-wpdb.php(3): wpdb->db_connect()
#1 /wordpress/wp-includes/load.php(2): wpdb->__construct('username_here', 'password_here', 'database_name_h...', 'localhost')
#2 /wordpress/wp-settings.php(2): require_wp_db()
#3 /wordpress/wp-config.php(102): require_once('/wordpress/wp-s...')
#4 /wordpress/wp-load.php(2): require_once('/wordpress/wp-c...')
#5 /internal/eval.php(7): require('/wordpress/wp-l...')
#6 {main}
thrown in /wordpress/wp-includes/class-wpdb.php on line 3
Error: PHP.run() failed with exit code 255 and the following output: PHP Fatal error: Uncaught Error: Call to undefined function mysqli_report() in /wordpress/wp-includes/class-wpdb.php:3
Stack trace:
#0 /wordpress/wp-includes/class-wpdb.php(3): wpdb->db_connect()
#1 /wordpress/wp-includes/load.php(2): wpdb->__construct('username_here', 'password_here', 'database_name_h...', 'localhost')
#2 /wordpress/wp-settings.php(2): require_wp_db()
#3 /wordpress/wp-config.php(102): require_once('/wordpress/wp-s...')
#4 /wordpress/wp-load.php(2): require_once('/wordpress/wp-c...')
#5 /internal/eval.php(7): require('/wordpress/wp-l...')
#6 {main}
thrown in /wordpress/wp-includes/class-wpdb.php on line 3
at PHP.run (https://playground.wordpress.net/worker-thread-33db168f.js:53:1888)
at async isWordPressInstalled (https://playground.wordpress.net/worker-thread-33db168f.js:108:1960)
at async bootWordPress (https://playground.wordpress.net/worker-thread-33db168f.js:108:1763)
at async PlaygroundWorkerEndpoint.boot (https://playground.wordpress.net/worker-thread-33db168f.js:801:2766)
|
The text was updated successfully, but these errors were encountered: