Uh oh!
There was an error while loading. Please reload this page.
[stable22] Fix in locking cache check - #27826
Conversation
The intention obviously was to check whether $lockingCacheClass is defined, and existing class, and available. It was however checked whether the $distributedCacheClass is an existing class, which would have caused an exception already in the previous distributed cache check. Signed-off-by: MichaIng <micha@dietpi.com>
How to tell @backportbot-nextcloud to assign stable22 backports to Nextcloud 22.0.1 milestone from now on? Failed test
Not related, of course. |
Pytal
commented
Jul 6, 2021
Take a look at https://github.com/nextcloud/backportbot/blob/01b844872191d6d116b8e0d936807b3f00c46c14/lib/backport.js#L5-L31 |
Okay I guess Nextcloud 22 was only used as it was still open and the first open matching major version milestone is used. I closed it in the meantime (and migrated all assigned PRs) so next |
Someone forgot to close the other milestone as part of the release procedure. It's done already but not retroactive |
skjnldsv
commented
Jul 7, 2021
The script failed |
nickvergessen
commented
Jul 7, 2021
Failing test is unrelated |
backport of #27818