-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Error - ValueError: str_repeat(): Argument #2 ($times) must be greater than or equal to 0 #29023
Comments
Can you run |
I've got some logs on this too while upgrading from 21.0.5 to 22.2.0, but no crash 💥
|
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Yes, the upgrade goes on with I can only (always) trown this on major upgrades (21>22) not on minor. |
The correct workaround to not run into that mentioned problem is:
In that case you not get that error. Apps get disabled / enabled on step 3. |
Ok i'll give it a try, as I was running EDIT: confirmed #29023 (comment) is working as workaround, thanks. |
I also just upgraded from 22.2.3 to 23.0.0 and ran into that error via running |
I wanted to go from 22.1.0.1 to 22.2.3.0, in my place the 'app/mail' has a problem. |
For everyone having that issue, can you all confirm by voting with 👍 that you are running php 8? cc @kinimodmeyer @solracsf @kesselb @fenvarien @fwolfst @LordSimal @dmothes @herndlm @jaakristioja @KatsuroKurosaki @z3ntu @VeijoPesonen @devi69 @Musikolo |
got this today on php8 also. |
observed the following: the issue happened when occ upgrade was run through updater.phar (ran through Ansible). I'm wondering if updater.phar itself is running the command in a shell environment not properly configured so that the progress bar would fail ? |
Comparing three different such reports I see that this is caused by |
I think I could narrow it down. It's our custom formatter that we use during the upgrade: server/core/Command/Upgrade.php Lines 86 to 90 in 0e29dc8
If I adjust the I'm having a closer look with the debugger. Edit: bingo |
How to use GitHub
Steps to reproduce
Expected behaviour
System should not crash and be broken
Actual behaviour
restart upgrade throws the exact same error.
if you make the upgrade step without the updater.phar it went through.
i had such a error on last upgrade too but on circles nextcloud/circles#807
The text was updated successfully, but these errors were encountered: