You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
This causes me an error when I run any wp cli command:
Fatal error: Declaration of Illuminate\Container\Container::get(string $id) must be compatible with Psr\Container\ContainerInterface::get($id) in /srv/www/bedrock-ds/current/vendor/illuminate/container/Container.php on line 739
The reason will be displayed to describe this comment to others. Learn more.
What are your other dependencies and plugins? The Psr\Container\ContainerInterface signature was updated in v1.1.0 of psr/container, and you shouldn't actually be able to install a version older than that alongside illuminate/container:^11.0. Some other dependency (more likely a plugin) may be breaking this by bundling a really old version of psr/container.
The reason will be displayed to describe this comment to others. Learn more.
@retlehs So the conflict is with the global WP-CLI install and its dependency on psr/container, not any two dependencies within the WordPress project, right? I guess I would think that anytime Acorn was loaded in the context of a WP-CLI command this would happen, but I'm clearly missing something.
566407b
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 causes me an error when I run any wp cli command:
Fatal error: Declaration of Illuminate\Container\Container::get(string $id) must be compatible with Psr\Container\ContainerInterface::get($id) in /srv/www/bedrock-ds/current/vendor/illuminate/container/Container.php on line 739
I'm using latest acorn
566407b
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.
What are your other dependencies and plugins? The
Psr\Container\ContainerInterface
signature was updated in v1.1.0 ofpsr/container
, and you shouldn't actually be able to install a version older than that alongsideilluminate/container:^11.0
. Some other dependency (more likely a plugin) may be breaking this by bundling a really old version ofpsr/container
.566407b
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.
@ethanclevenger91 as mentioned by @LucasDemea, this happens when using Acorn.
https://github.com/wp-cli/wp-cli-bundle/blob/6d3fc1b6ae99280ad6493887792fcb084fa6718f/composer.lock#L5211-L5212
566407b
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.
@retlehs So the conflict is with the global WP-CLI install and its dependency on
psr/container
, not any two dependencies within the WordPress project, right? I guess I would think that anytime Acorn was loaded in the context of a WP-CLI command this would happen, but I'm clearly missing something.