Phil Tyler

Related: https://github.com/pantheon-systems/pantheon-advanced-page-cache/issues/178 Fixed in #279

Related/duplicate: https://github.com/wp-cli/extension-command/issues/216

The root cause of why the update didn't apply is different (i.e. auth failure vs write access), but the behavior is the same— WP-CLI reports the wrong status after the...

We've encountered this same issue with licensed plugins with an invalid/missing license, as it turns out, it seems to be related to the order the plugins are updated— if a...

A shorter, easier test to reproduce: ``` # The incorrect behavior when the second of two updates errors $ wp plugin install akismet --version=4.0 --force $ wp plugin install wordpress-importer...

Details on this being a bug in WordPress Core, not WP-CLI: https://core.trac.wordpress.org/ticket/53002

Yep, this looks like this is related if not a dupe of #4944. Here's [my php.ini](https://gist.github.com/pwtyler/30de552227bc1b8cdce615dd3530db08) I am almost positive it's all the defaults from homebrew here. Shortcutting to what...

I thought I closed this some time back— I was able to fix the stderr behavior with an .ini adjustment, and the repeated notices/warnings is already captured in #4944.

Yep this was resolved with WP 5.9.

This linked core fix was resolved with WP 5.9. WP-CLI _could_ be patched to work around the behavior for earlier versions of WordPress, but I expect this issue could simply...