As discussed in 🐛 "Field field_last_password_reset is unknown" while importing configuration on site without password_policy activated Fixed , it would be beneficial to move the initial processing of all user accounts into a queue in order to prevent memory time outs when there are large numbers of users needing to be updated. This issue doesn't appear when the password policy module is installed at the beginning of a site build, but if a site has thousands of users, the current process of adding the password policy setting onto each user at install is untenable.
Update the hook_install function to instead use Drupal's queue system to process necessary password updates.
Suggested alternate resolution #2983448: Refactor hook_install logic to expire passwords for existing users →
Needs work
4.0
Code
The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Critical errors should be reserved for fatal errors and similar. Moving this to major.
Given this issue has been quiet a few years, I'm moving it to normal priority. And it needs a reroll.