From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 37168-done@debbugs.gnu.org
Subject: bug#37168: debbugs: Make bug list update asynchronous
Date: Wed, 25 May 2022 21:10:11 +0200 [thread overview]
Message-ID: <87zgj5mnsc.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmmqXpcK7bbEh=wiqAiTa7iy0TECky1QkUoYrUhQjJU7qQ@mail.gmail.com> (Stefan Kangas's message of "Wed, 25 May 2022 14:02:18 -0500")
Stefan Kangas <stefan@marxist.se> writes:
Hi Stefan,
>> Bug retrieving happens in two phases. The first phase, getting the bug
>> numbers in question, cannot be performed asynchronously, because it is
>> just one request to the debbugs server.
>>
>> The second phase, getting information per bug number, happens already
>> asynchronously. The debbugs server is requested to return maximum
>> debbugs-max-hits-per-request per request; several requests are sent in
>> parallel to the server. Furthermore, debbugs caches the results, so the
>> next time information for an already known bug number is taken from the
>> cache.
>>
>> However, debbugs waits until all parallel requests have been served by
>> the debbugs server, before it begins to show the tabulated list. This
>> might be done asynchronously as well. Will check, what's possible.
>
> Any news regarding this? If no progress is possible here, perhaps the
> bug should be closed. WDYT?
No, nothing happened. And since there aren't no further complaints from
other users, I believe we could leave it as it is. Closing the bug.
Best regards, Michael.
prev parent reply other threads:[~2022-05-25 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 21:59 bug#37168: debbugs: Make bug list update asynchronous Stefan Kangas
2019-08-24 7:19 ` Michael Albinus
2019-08-24 12:47 ` Stefan Kangas
2019-08-24 14:40 ` Michael Albinus
2019-08-24 14:47 ` Stefan Kangas
2019-08-24 18:28 ` Michael Albinus
2022-05-25 19:02 ` Stefan Kangas
2022-05-25 19:10 ` Michael Albinus [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgj5mnsc.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=37168-done@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).