Introduce wp profile queries command

[Copilot]

Adds a new wp profile queries command to display database queries executed during a WordPress request with timing information and optional filtering by hook or callback.

Changes

• Command.php: New queries() method that runs WordPress profiling, collects queries from $wpdb->queries, and outputs them with configurable fields and filtering. Includes proper handling for both --hook and --callback parameters used together, and explicit filtering logic to skip loggers without callbacks when callback filtering is requested.
• QueryLogger.php: Simple data container for query metadata (SQL, execution time, caller, hook, callback)
• Logger.php: Enhanced to track query_indices array during stop(), enabling accurate query-to-hook/callback mapping. The query_indices array is now properly reset in stop() method to ensure clean state for reused loggers.
• Formatter.php: Fixed to properly handle non-numeric fields ('query', 'caller', 'hook', 'callback') by skipping them during total calculations and adding numeric validation to prevent PHP warnings
• Tests: Added features/profile-queries.feature with scenarios for basic listing, filtering, and output formats. Tests include custom mu-plugins that execute specific database queries to verify functionality.

Usage

# All queries with timing
wp profile queries --fields=query,time

# Queries from specific hook
wp profile queries --hook=init --fields=query,time,callback

# Queries from specific callback
wp profile queries --callback='WP_Query->get_posts()' --fields=query,time

# Filter by both hook and callback
wp profile queries --hook=init --callback=my_function --fields=query,time

# Sort by execution time
wp profile queries --orderby=time --order=DESC --fields=query,time

Filtering works by tracking which query indices each Logger executes (via query_offset range), then matching those indices to hook/callback names when filtering is requested. When both --hook and --callback are provided, the command profiles all hooks and then filters to show only queries that match both criteria.

• Fixes Introduce wp profile queries #130

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Introduce wp profile queries</issue_title>
<issue_description>It would be helpful to be able to see all queries and how much time they're taking.

Also make it possible to show actual queries for (a) a specific callback or (b) all queries within a specific hook</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Introduce wp profile queries #130

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[swissspidy]

@copilot There's lots of PHP warnings "Warning: A non-numeric value encountered in src/Formatter.php on line 134" in tests for this new code. Please fix the root cause.

[Copilot]

@copilot There's lots of PHP warnings "Warning: A non-numeric value encountered in src/Formatter.php on line 134" in tests for this new code. Please fix the root cause.

Fixed by adding non-numeric field detection in Formatter.php. The code now skips string fields ('query', 'caller', 'hook', 'callback') when calculating totals and includes an is_numeric() check before summing values to prevent the warnings. (commit 28e1e4d)

[Copilot]

Pull Request Overview

Copilot reviewed 8 out of 8 changed files in this pull request and generated 7 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] Potential issue with query map overwriting. When multiple loggers track the same query index (e.g., nested hooks), the check ! isset( $query_map[ $query_index ] ) at line 602 prevents overwriting. This means the first logger's hook/callback will be used, but in nested scenarios, this might not be the most specific or accurate mapping. Consider whether the first-logger-wins approach is the intended behavior, or if you need to track multiple hooks/callbacks per query.

[Copilot]

[nitpick] Performance consideration: The nested loop structure (lines 583-610 and 616-630) could be inefficient for sites with many queries and hooks. For N loggers and M queries, this is O(N*Q + M) where Q is queries per logger. If $wpdb->queries contains thousands of entries, this might be slow. Consider optimizing by building the query map in a single pass if performance becomes an issue, though the current implementation is clear and correct for typical use cases.

[Copilot]

The $query_indices array is not reset in the stop() method, unlike other tracking properties (e.g., $query_offset is set to null on line 111). If a Logger instance is reused by calling start() and stop() multiple times, the $query_indices array will accumulate indices across multiple runs. Consider resetting $this->query_indices = array(); in the stop() method or at the start of start() method to ensure clean state for reused loggers, or document that loggers should not be reused.

[Copilot]

When both --hook and --callback are provided, the profiler setup logic only uses the hook value. The condition on line 571 (elseif ( $callback )) will never be reached when both are present. This means the profiler won't track all hooks to find the specific callback, which could lead to incomplete filtering. Consider handling the case where both are provided explicitly, or adjust the logic to ensure both parameters are considered properly.