Algolia search results is inconsistent when using pagination #2020
Description
Describe the bug
Algolia nbHits response (max results available for given query) is inconsistent when performing further requests using pagination. I found some search queries which would fail at some point when a user tries to navigate to the end of the list. This happens because on initial response Algolia returns nbHits: 200, and on some page for the same query just adding offset it returns nbHits: 100, even if 100+ hits already loaded
do not test it on queries which returns 1000+ results as it would fail because of Algolia maximum hits limit; see #1996
do not click on a last page button as it would fail becase of the same issue with limits
This should not be started before #1996 is resolved
Additional context
Step to reproduce:
- switch to Aloglia search
- use table view in search results and 10 items per page
- turn instant search off (actually it's reproducible in both states, but just for a clea testing do not user instant search)
- search for "clarissa"
- you could see either 206(sometimes 207) or 41 results
- if you get 41 results - try to refresh the page, start search again until you get 206 results
- navigate page by page till the end of the list
- see empty page and total results changed at some point
Additionally
- switch to another count per page - it is reproducible for any at some point
- try "marinara" search instead and do same actions
- go to https://www.jsdelivr.com/ and try to search for marinara or clarissa and navigate to the last page in pagination. It would fail at some point meaning that issue is persistent for other services using Algolia
Screenshots
