-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fixes infinitely repeating LDPA search results with PHP <= 7.2 #21108
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
Conversation
|
/backport to stable19 |
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
9a9f830 to
15008a1
Compare
rullzer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐘
juliusknorr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good, however I fail to reproduce the issue on my PHP 7.2 instance, so I cannot verify that it actually works 🙈
| if (!$this->hasMoreResults()) { | ||
| // when the cookie is reset with != 0 offset, there are no further | ||
| // results, so stop. This if block is not necessary with new API | ||
| // and can be removed with dropping PHP 7.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why can we remove this block when we drop PHP 7.2 when this solves an issue that occured on 7.4 (#20745)?
Or is that new API not implemented yet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I failed to reproduce it on 7.4 for some unknown reason. Ought to double check and remove this part of the comment.
|
One word of caution for those applying this fix (and maybe something that can be automatically solved in the release): This bug caused the Now, this fix would solve the issue regarding the ever-increasing offset, but the cron job now fails before that can happen because of the recursion error. It's solved by manually forcing the offset to zero. |
fixes #20745