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
I wanted to run this past the maintainers before preparing a pull request:
When running wp core update --force, the process will still abort if another update had been attempted but failed (for example, if the core_updater.lock option was left behind after a failed update). Would it make sense for --force to explicitly clear any locks that might exist, or might this be better served by a new option (e.g. --ignore-lock)?
The text was updated successfully, but these errors were encountered:
Right now, the help already provides a solution to this by explaining the problem and providing a separate command as a solution:
If you see "Error: Another update is currently in progress.", you may
need to run `wp option delete core_updater.lock` after verifying another
update isn't actually running.
I'm not sure having --force remove the lock automatically (and potentially corrupting the install because an update was indeed in progress) is an improvement...
Maybe we can make the above text appear when you actually hit the issue?
I wanted to run this past the maintainers before preparing a pull request:
When running
wp core update --force
, the process will still abort if another update had been attempted but failed (for example, if thecore_updater.lock
option was left behind after a failed update). Would it make sense for--force
to explicitly clear any locks that might exist, or might this be better served by a new option (e.g.--ignore-lock
)?The text was updated successfully, but these errors were encountered: