Erratic results when searching with Live API

I also faced the same issue:

1. Sometimes the API takes too long to fetch the results, even if the internet speed is good.
2. In case incomplete results are cached, even with the cache clear it is not resetting the results, I had to reinstall the module
3. In my case it could only fetch around 24 results out of 8k and pagination till 2 pages worked, The pager appeared but the other pages had not data, trying to replicate to get a screenshot but no success yet.

Interesting point on pagination. I'd suggest it makes no sense to try to send back all the results since there could be a lot, and most users won't go past the first page or two. So the API should return the first X results, and the total number of matches, and the front end should be able to request additional pages as required.

I agree, on the initial page load instead of loading all the results we should load only the first page results and load the next results on the fly based on the page number.

Also, there will need to be some form of cache invalidation. If maintainers update their modules and don't see the updates in PB fairly quickly, they will lose confidence in the system. Perhaps the API could send a list of updated module IDs, and PB would discard any results containing those modules from its cache.

A few more issues, filters behaving weirdly. Overall very unstable, I would say.

https://www.awesomescreenshot.com/video/30109604?key=65c4ed47642ae06794a...

I can't reproduce the spottiness, even simulating 3G right now. AND, there's an open separate issue for creating a UI and a Drush-based way of resetting the Key-Value store.

So, can this be closed (outdated) or can other folks still replicate the spottiness here?

Now, we need to click the search icon after entering text, so it seems all points raised in this issue are outdated. Therefore, this issue can be marked as closed (outdated).

Closing this issue as Closed(cannot reproduce),