-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Fix undefined index and consequential damages in versions code #23295
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
Fix undefined index and consequential damages in versions code #23295
Conversation
|
/backport to stable20 |
|
/backport to stable19 |
|
Make sense. I also think there are some reports around for this. |
|
@ChristophWurst I added a commit that added the changes the @nickvergessen proposed, because I think that is the better approach to deal with this. |
|
DB tests are not happy. Seems to be the "random fail" but it failed on all DBs here, so not sure its unrelated? |
Unfortunately also happening with other PRs right now |
If the user has no space and there are no versions, there won't be an `all` index in the versions entry. Hence this triggers a warning and becomes `null`, afterwards `count`, `foreach` and friends will happily throw even more warnings and errors because they don't want to play with `null`. Thus adding a fallback to an empty array. Signed-off-by: Christoph Wurst <[email protected]>
Signed-off-by: Morris Jobke <[email protected]>
28cd924 to
6ce05bc
Compare
Fixed with #23391 |
|
🤖 beep boop beep 🤖 Here are the logs for the failed build: Status of 34039: failuresqliteShow full logmysql8.0-php7.4
|
If the user has no space and there are no versions, there won't be an
allindex in the versions entry. Hence this triggers a warning andbecomes
null, afterwardscount,foreachand friends will happilythrow even more warnings and errors because they don't want to play with
null. Thus adding a fallback to an empty array.