| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. Co-authored-by: westonruter <westonruter@git.wordpress.org> Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: emrikol <emrikol@git.wordpress.org> To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 2.50000% with 39 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## trunk #2159 +/- ##
==========================================
- Coverage 68.81% 68.54% -0.27%
==========================================
Files 90 90
Lines 8006 8037 +31
==========================================
Hits 5509 5509
- Misses 2497 2528 +31
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
Build for testing: performance-lab.zip |
Sorry, something went wrong.
|
PR fixes issue in testing: #2158 (comment) |
Sorry, something went wrong.
There was a problem hiding this comment.
Code looks good!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #2158
This addresses issues which may arise when using a database implementation which doesn't construct $wpdb->queries in the same way as core does, namely when a logged query is not an indexed array or it it doesn't have a float at index 1. This can happen when using a custom save_query_callback in HyperDB, for example. This essentially builds upon the existing type checking for odd database implementations which don't define $wpdb->queries. In both cases, notices are now emitted before aborting.
If $wpdb->queries is absent or not an array, this notice is emitted:
If a saved query array doesn't have the expected elapsed time as the second argument, then this notice is emitted:
Otherwise, if all is good, then the before-template-db-queries server timing entry is sent: