From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#56332: 29.0.50; Large gnus imap groups; articles incorrectly marked as read (old) Date: Sun, 03 Jul 2022 12:59:31 +0200 Message-ID: <87tu7ybgx8.fsf@gnus.org> References: <875ykh9vo1.fsf@md5i.com> <87o7y9xjhd.fsf@gnus.org> <87ilohxiu0.fsf@gnus.org> <87letc7rqn.fsf@md5i.com> <87mtdr3esq.fsf@gnus.org> <87r1334mfm.fsf@md5i.com> <87r133zgfu.fsf@gnus.org> <87ilof4i8x.fsf@md5i.com> <877d4v4gez.fsf@md5i.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4099"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 56332@debbugs.gnu.org To: Michael Welsh Duggan Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jul 03 13:01:21 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o7xLt-0000tY-R6 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 03 Jul 2022 13:01:21 +0200 Original-Received: from localhost ([::1]:57044 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o7xLs-0005QN-PM for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 03 Jul 2022 07:01:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48700) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o7xKc-000589-MY for bug-gnu-emacs@gnu.org; Sun, 03 Jul 2022 07:00:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49504) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o7xKc-0002X9-D4 for bug-gnu-emacs@gnu.org; Sun, 03 Jul 2022 07:00:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o7xKc-0005Pl-B2 for bug-gnu-emacs@gnu.org; Sun, 03 Jul 2022 07:00:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 03 Jul 2022 11:00:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56332 X-GNU-PR-Package: emacs Original-Received: via spool by 56332-submit@debbugs.gnu.org id=B56332.165684598920769 (code B ref 56332); Sun, 03 Jul 2022 11:00:02 +0000 Original-Received: (at 56332) by debbugs.gnu.org; 3 Jul 2022 10:59:49 +0000 Original-Received: from localhost ([127.0.0.1]:43401 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o7xKM-0005Op-79 for submit@debbugs.gnu.org; Sun, 03 Jul 2022 06:59:49 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:49278) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o7xKJ-0005Ob-N3 for 56332@debbugs.gnu.org; Sun, 03 Jul 2022 06:59:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=NzB4IyqB4j4IbStEN4kiO5PeYw63hyHBQvfDYlhXHls=; b=bcBIbPBRfsJl6fyS6QU31Hrvno DWNrOvsHCwhEcqRk0I0ykapdh8yyfRNqBe29bsrDa7kwY3kg4VeP6QvnOvbS5SX2OF8b8VKW6ll6s pcPn9x7KCiuNP3/4H2QgjuO7WB9YidsFYZrnGceMRdbAOBxECAEEt1gFa5BNJPg1a2bA=; Original-Received: from [84.212.220.105] (helo=joga) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o7xK8-0004B8-Ez; Sun, 03 Jul 2022 12:59:35 +0200 In-Reply-To: <877d4v4gez.fsf@md5i.com> (Michael Welsh Duggan's message of "Sat, 02 Jul 2022 12:40:04 -0400") Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAFVBMVEUyJSqZZV+wgnnL pp/x29L9+/n///+noQVCAAAAAWJLR0QGYWa4fQAAAAd0SU1FB+YHAwo5HyJHJFgAAAGiSURBVDjL lZRbdoQgDIYJMwswOH0XnL5XoAtoxRUU9r+VJtxG7cxD4zkc5DPwJyQK8W8DRIThCUBjjNKY7cDN 7MiMRkPPHtBqCIGQM4o8AAYonoFtC6tz+uAgPK+nQOSkgEFKMTidX+X8IaRbaKbuWyKw2uIAoITE iaejZ5dV17AmOWiVgRgdoeogQKMEXb9CAssjEQqmqu9Gqj6aGDUabOCdTm8AII/l5XMH8mZtxnq/ NHQy1YlMDOpnktS1FFwZ/BR96CY6oJIbg8iBoLI5AnycTcmyg2pBFnBJxaKdrSkOeQRfQbJ0Z7wh lJuctwboGku+C+jrlGHlVxzAmOEMNFK9zEWZSGlPlJ1dLZY9SMFzURTVWzqi1dbw/oIaZngJthfA n4DrZdFSEotiZ9p1yOoSs2+ryJ52Am7jI9zUwXuLm4q1lypf/VtPiCcH3Y9YPxtYxtXZ3m+X4HsI aHbdI8O9rG8xLMr0nQS4cStqQ/pG3LUb5kDigrcYTm04hshtcKXxCIjYPAZ7AiKX2oWjEE+MysPR XpBr+ECoy0z5qyjEXx1Skfhmv1qVAAAAJXRFWHRkYXRlOmNyZWF0ZQAyMDIyLTA3LTAzVDEwOjU3 OjMxKzAwOjAwZ0bK0QAAACV0RVh0ZGF0ZTptb2RpZnkAMjAyMi0wNy0wM1QxMDo1NzozMSswMDow MBYbcm0AAAAASUVORK5CYII= X-Now-Playing: Eurythmics's _1984 (For The Love Of Big Brother)_: "Greetings From A Dead Man" X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:235981 Archived-At: Michael Welsh Duggan writes: >> I will also note that, though the fetch data responses are not in order, >> the fetch completion messages are in order. Though I'm not certain they >> have to be. Here's some data from the Internet, though I can't find >> anything in the standard that seems to either confirm or refute this >> data: >> >> https://stackoverflow.com/questions/26034086/does-imap-guarantee-that-servers-send-responses-in-order >> >> Wouldn't another solution be to sort the results by UID? They are being >> requested in UID order, after all. > > You should probably read this section of the RFC, especially the > "Note:". > > https://datatracker.ietf.org/doc/html/rfc3501#section-5.5 Reading that, I'm not sure whether the completion messages are guaranteed to be in order, either, so I've now changed the code to avoid streaming altogether. Can you check whether that fixes the problem? (If the completion messages are guaranteed to be in order, we could change it back to using streaming and then just reorder the results, as you suggest, but I'm not sure it's worth it even if it is guaranteed.) -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no