Uh oh!
There was an error while loading. Please reload this page.
Fix undefined index and consequential damages in versions code - #23295
Conversation
ChristophWurst
commented
Oct 8, 2020
/backport to stable20 |
ChristophWurst
commented
Oct 8, 2020
/backport to stable19 |
kesselb
commented
Oct 8, 2020
Make sense. I also think there are some reports around for this. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
MorrisJobke
commented
Oct 9, 2020
@ChristophWurst I added a commit that added the changes the @nickvergessen proposed, because I think that is the better approach to deal with this. |
Uh oh!
There was an error while loading. Please reload this page.
nickvergessen
commented
Oct 12, 2020
DB tests are not happy. Seems to be the "random fail" but it failed on all DBs here, so not sure its unrelated? |
ChristophWurst
commented
Oct 12, 2020
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 <christoph@winzerhof-wurst.at>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
28cd924 to
6ce05bcCompareMorrisJobke
commented
Oct 12, 2020
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.