dont crash if suitetalk returns empty <platformCore:searchRowList/> #574
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The client should just yield the blank page returned instead of crashing, but to ever receive this seems like a bug in suitetalk since we're using results_in_batches but on the final page sometimes a successful result is returned with no rows, probably because the underlying data no longer matches the search since our pagination takes an hour or so and we're running it across day boundaries, but you'd think search_id would represent an isolated view of the data we're paginating. we haven't captured the log to see if total_records changes, but obviously total_pages doesn't since it successfully accepts page_index but just doesn't return any rows.