-
Notifications
You must be signed in to change notification settings - Fork 228
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
Container V4 service provider lied about providing (options_debug) service #6865
Comments
Reproduce the issue ✅Yes Identify the root cause ✅This happens because Scope a solution ✅The Estimate the effort ✅Effort XS |
Looks good to me |
@mostafa-hisham I'm getting the error, this is after adding options_debug to
|
@Khadreal this means that the class |
@CrochetFeve0251 yes, but the class is defined. Could it be because this class [Update] |
@Khadreal I think there is something weird going on with the parameters given. Some |
Will be tested by Service team: https://github.com/wp-media/rucss-debug-tool/pull/16 |
…ons_debug) service (#6902) Co-authored-by: Mathieu Lamiot <[email protected]>
Before submitting an issue please check that you’ve completed the following steps:
Describe the bug
After updating the container to V4, we cannot use
options_debug
in Rucss debug tool.we are getting this error
With @CrochetFeve0251 help we checked and in wp-rocket we are bailing out here and we don't serve it
To Reproduce
Steps to reproduce the behavior:
Expected behavior
We should use the
options_debug
like this$container->get('options_debug' ),
Screenshots

The text was updated successfully, but these errors were encountered: