Improve output when queuing with the --page= parameter

Created on 21 November 2023, 10 months ago

Problem/Motivation

This issue is a follow up to feature request 3397001 ✨ Ability to resume a queue operation from where it failed Fixed .

The paging feature works and queuing can be resumed at various pages in the result set.

However, as noted in that issue, the user facing output is a little bit confusing/misleading.

I do think, now that I see it, that the output is off.

[notice] Starting at page 1, found 7,207 item(s) of type 'Photograph' in the Orange Logic Search API results.
0/25 [>---------------------------] 0%

It seems we would want the count of found items to change depending on which page we start from. But I guess that should be a separate issue. The point right now is simply being able to resume. And we got that.

The number of items found is the _total_ number of items in the full result set, regardless of how many items will be returned when starting from a certain page.

In other words, if there are 100 items, and we are paging at 10 per item, and do not pass a --page option, we would expect the feedback to say "found 100 item(s)...". But if we pass --page=5 option, we should see "found 50 item(s)". <--We can argue about that, but that's what this issue is for... figuring out the output to the user when using the --page option.

πŸ› Bug report
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States apotek

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024