Allow cache-rebuild to fix more things #6243
Merged
Conversation
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
|
Drush cr not rebuilding the container has been observed in https://www.drupal.org/project/entity_usage/issues/3509039 for example. |
|
Nice find. This certainly fixes the scenario described in the OP. Otherwise, the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If we add this annotation the cache rebuild command becomes even more useful and can recover from more terminal issues.
For example if you change the Drupal core service name cache.backend.database to cache.backend.databas and do a drush cr you'll get an error. On HEAD if you go back and fix this and then run drush cr again it'll still be broken. With this change drush cr is capable of fixing the site.