GNU bug report logs - #37168
debbugs: Make bug list update asynchronous

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#37168: closed (debbugs: Make bug list update asynchronous)
Date: Wed, 25 May 2022 19:11:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 25 May 2022 21:10:11 +0200
with message-id <87zgj5mnsc.fsf <at> gmx.de>
and subject line Re: bug#37168: debbugs: Make bug list update asynchronous
has caused the debbugs.gnu.org bug report #37168,
regarding debbugs: Make bug list update asynchronous
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
37168: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37168
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Stefan Kangas <stefan <at> marxist.se>
To: bug-gnu-emacs <at> gnu.org
Subject: debbugs: Make bug list update asynchronous
Date: Fri, 23 Aug 2019 23:59:10 +0200

Severity: wishlist

When I type:

M-x debbugs-gnu RET ,minor,wishlist RET

It takes a long time to load on my machine, and it freezes my entire
Emacs session while I wait.  It would be very nice if this operation
could be made to work asynchronously.

Thanks,
Stefan Kangas

[Message part 3 (message/rfc822, inline)]

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 37168-done <at> debbugs.gnu.org
Subject: Re: bug#37168: debbugs: Make bug list update asynchronous
Date: Wed, 25 May 2022 21:10:11 +0200

Stefan Kangas <stefan <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.