-
Notifications
You must be signed in to change notification settings - Fork 101
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
Disregard transient cache in perflab_query_plugin_info() when a plugin is absent #1694
base: trunk
Are you sure you want to change the base?
Conversation
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
__( 'Plugin not found in WordPress.org API response.', 'performance-lab' ) | ||
); | ||
// Cache the fact that the plugin was not found. | ||
$plugins[ $current_plugin_slug ] = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of storing false
here, what about storing the WP_Error
instance? As it stands right now, there are two conditions resulting in false
being logged, which conflates these two error scenarios which we tried to get rid of in #1651 to assist with debugging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this makes sense to me. We probably shouldn't store the WP_Error
instance though, but just its data, since storing PHP class instances is a bit unpredictable with what would happen in different object cache implementations.
@@ -101,9 +102,14 @@ function perflab_query_plugin_info( string $plugin_slug ) { | |||
} | |||
} | |||
|
|||
if ( ! isset( $plugins[ $plugin_slug ] ) ) { | |||
// Cache the fact that the plugin was not found. | |||
$plugins[ $plugin_slug ] = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above about storing a WP_Error
instance instead.
if ( false === $plugins[ $plugin_slug ] ) { | ||
// Plugin was requested before and not found. | ||
return new WP_Error( | ||
'plugin_not_found', | ||
__( 'Plugin not found in cached API response.', 'performance-lab' ) | ||
); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If $plugins[ $plugin_slug ]
is either an array
or a WP_Error
, then this can just return that.
if ( false === $plugins[ $plugin_slug ] ) { | |
// Plugin was requested before and not found. | |
return new WP_Error( | |
'plugin_not_found', | |
__( 'Plugin not found in cached API response.', 'performance-lab' ) | |
); | |
} |
// Cache the fact that the plugin was not found. | ||
$plugins[ $plugin_slug ] = false; | ||
} | ||
|
||
set_transient( $transient_key, $plugins, HOUR_IN_SECONDS ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here I think it would be good to check if there was an error condition, and if so, set the expiration to 1 minute instead of HOUR_IN_SECONDS
.
There are still these error scenarios that isn't getting cached: performance/plugins/performance-lab/includes/admin/plugins.php Lines 58 to 72 in 2a344c9
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @b1ink0! This looks good, just one thing that needs to be fixed I think.
|
||
set_transient( $transient_key, $plugins, MINUTE_IN_SECONDS ); | ||
} else { | ||
set_transient( $transient_key, $plugins, HOUR_IN_SECONDS ); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This differentiation does not happen in the correct clause. We should use a shorter cache duration in case of any error, not just in the case of this specific error.
I think it would be most straightforward to implement this via a boolean flag like $has_errors
that is set if anywhere in the (uncached) logic an error is set. Then the code here could be changed like:
set_transient( $transient_key, $plugins, MINUTE_IN_SECONDS ); | |
} else { | |
set_transient( $transient_key, $plugins, HOUR_IN_SECONDS ); | |
} | |
} | |
if ( $has_errors ) { | |
set_transient( $transient_key, $plugins, MINUTE_IN_SECONDS ); | |
} else { | |
set_transient( $transient_key, $plugins, HOUR_IN_SECONDS ); | |
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@b1ink0 There are two points of follow-up feedback, though some of them have overlap with #1691. But since this is broken too and affected by the same logic, maybe we should work towards a solution that addresses both?
cc @westonruter
if ( is_wp_error( $response ) ) { | ||
return new WP_Error( | ||
'api_error', | ||
sprintf( | ||
/* translators: %s: API error message */ | ||
__( 'Failed to retrieve plugins data from WordPress.org API: %s', 'performance-lab' ), | ||
$response->get_error_message() | ||
) | ||
$plugins[ $plugin_slug ] = array( | ||
'error' => array( | ||
'code' => 'api_error', | ||
'message' => sprintf( | ||
/* translators: %s: API error message */ | ||
__( 'Failed to retrieve plugins data from WordPress.org API: %s', 'performance-lab' ), | ||
$response->get_error_message() | ||
), | ||
), | ||
); | ||
|
||
$has_errors = true; | ||
} | ||
|
||
// Check if the response contains plugins. | ||
if ( ! ( is_object( $response ) && property_exists( $response, 'plugins' ) ) ) { | ||
return new WP_Error( 'no_plugins', __( 'No plugins found in the API response.', 'performance-lab' ) ); | ||
if ( ! $has_errors && ! ( is_object( $response ) && property_exists( $response, 'plugins' ) ) ) { | ||
$plugins[ $plugin_slug ] = array( | ||
'error' => array( | ||
'code' => 'no_plugins', | ||
'message' => __( 'No plugins found in the API response.', 'performance-lab' ), | ||
), | ||
); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think for both of these scenarios we need to set the error for every single plugin of ours. In other words, iterate through the list from perflab_get_standalone_plugins()
and set the same error for every plugin's slug.
Otherwise, this can cause a problem where the API failing would cause the request to be issued for every single plugin, which would defeat the purpose of the transient cache and the combination of those plugin requests into a single API request (see #1542). This would effectively fix #1691, and since this PR is touching the exact same logic, I wonder whether we should go straight to a solution that addresses both issues.
if ( ! isset( $plugins[ $plugin_slug ] ) ) { | ||
// Cache the fact that the plugin was not found. | ||
$plugins[ $plugin_slug ] = array( | ||
'error' => array( | ||
'code' => 'plugin_not_found', | ||
'message' => __( 'Plugin not found in API response.', 'performance-lab' ), | ||
), | ||
); | ||
|
||
// Enqueue the required plugins slug by adding it to the queue. | ||
if ( isset( $plugin_data['requires_plugins'] ) && is_array( $plugin_data['requires_plugins'] ) ) { | ||
$plugin_queue = array_merge( $plugin_queue, $plugin_data['requires_plugins'] ); | ||
$has_errors = true; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I look at this again, what is this particular check needed for? Wouldn't this already be catered for by the check above in line 101?
Summary
Fixes #1617
Relevant technical choices
When a new feature plugin is published, it may not yet exist in the transient. Therefore, whenever one of the expected feature plugin is absent, we should act as if the transient was not set in the first place so that we can obtain the latest plugin info right away.
Logic for this to work:
false
.false
raise the error.This logic will make sure that the multiple request are not made for the plugin which is absent.