From: Hannes Laimer <h.laimer@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-api 1/1] fix #3450: api: add 'filter' parameter to queue DELETE endpoint
Date: Mon, 22 Sep 2025 12:15:28 +0200 [thread overview]
Message-ID: <6b75565c-61ad-4732-aae3-dfff953296fc@proxmox.com> (raw)
In-Reply-To: <20250922120925.30faeb65@rosa.proxmox.com>
On 22.09.25 12:09, Stoiko Ivanov wrote:
> Thanks for the patches, reviews and suggestions!
>
>
> On Mon, 22 Sep 2025 11:18:10 +0200
> Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
>
>> Am 22.09.25 um 10:58 schrieb Dominik Csapak:
>>> one high level comment and a few comments inline
>>>
>>> i get what you want to achieve here and this is what stoiko wrote in the
>>> bugreport, but from an UX perspective this could be bad. Since the
>>> mails shown on the gui might not match what will be deleted (e.g. new mails came in, in the meantime)
>>>
>>> would it maybe make more sense to have an approach with giving a list
>>> of ids to the backend? (@stoiko ?)
>>
>> That would be safer, as long as it can also handle at least 1k of mails
>> being processed I'd be fine with that.
>>
>> An alternative could be passing a cutoff timestamp from the newest mail
>> selected along, but an explicit list naturally is slightly simpler to
>> handle and to debug, so mostly just mentioning it for the sake of
>> completeness.
> looked at bugreport and the Queue GUI again - I think my idea back then
> was:
> * we already have a filter in the Deferred Mail panel
> * adding a checkbox for selection of multiple mails + one for all mail
> (that is displayed after the filter) and Removing the selected ones
> should help most users who need to clear up a queue most.
> AFICT - sending a list to the backend seems a sensible way to achieve that.
>
yes
so the "all" would be for the paginated list, right? I am not sure if
having 10-20+ pages worth of mail is realistic here
>
>> high-level: would then be naturally also nice to have for
>> delivering a (filtered) list of mails, or does anything speak
>> against that?
>
> That seems a worth-while addition as well!
>
>
>
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next prev parent reply other threads:[~2025-09-22 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 14:50 [pmg-devel] [PATCH pmg-api/pmg-gui 0/2] add support to delete multiple queue entries at once Hannes Laimer
2025-09-19 14:50 ` [pmg-devel] [PATCH pmg-api 1/1] fix #3450: api: add 'filter' parameter to queue DELETE endpoint Hannes Laimer
2025-09-22 8:58 ` Dominik Csapak
2025-09-22 9:18 ` Thomas Lamprecht
2025-09-22 10:09 ` Stoiko Ivanov
2025-09-22 10:15 ` Hannes Laimer [this message]
2025-09-22 9:19 ` Thomas Lamprecht
2025-09-19 14:50 ` [pmg-devel] [PATCH pmg-gui 1/1] fix #3450: ui: add button to delete all queue entries matching a filter Hannes Laimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b75565c-61ad-4732-aae3-dfff953296fc@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.