From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "J.P." Newsgroups: gmane.emacs.bugs,gmane.emacs.erc.general Subject: bug#59135: Receiving large files with ERC-DCC Date: Wed, 09 Nov 2022 06:00:35 -0800 Message-ID: <87sfisz0qk.fsf@neverwas.me> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11111"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-erc@gnu.org, 59135@debbugs.gnu.org To: Tohiko Looka Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Nov 09 15:01:23 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 1osldr-0002gU-6w for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 09 Nov 2022 15:01:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1osldZ-0003K2-Un; Wed, 09 Nov 2022 09:01:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1osldX-0003Id-MG for bug-gnu-emacs@gnu.org; Wed, 09 Nov 2022 09:01:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1osldW-0007Hp-8Y for bug-gnu-emacs@gnu.org; Wed, 09 Nov 2022 09:01:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1osldW-0003or-3G for bug-gnu-emacs@gnu.org; Wed, 09 Nov 2022 09:01:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: "J.P." Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 09 Nov 2022 14:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59135 X-GNU-PR-Package: emacs Original-Received: via spool by 59135-submit@debbugs.gnu.org id=B59135.166800244814656 (code B ref 59135); Wed, 09 Nov 2022 14:01:02 +0000 Original-Received: (at 59135) by debbugs.gnu.org; 9 Nov 2022 14:00:48 +0000 Original-Received: from localhost ([127.0.0.1]:39367 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1osldI-0003oJ-EN for submit@debbugs.gnu.org; Wed, 09 Nov 2022 09:00:48 -0500 Original-Received: from mail-108-mta41.mxroute.com ([136.175.108.41]:37499) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1osldG-0003o6-IU for 59135@debbugs.gnu.org; Wed, 09 Nov 2022 09:00:47 -0500 Original-Received: from mail-111-mta2.mxroute.com ([136.175.111.2] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta41.mxroute.com (ZoneMTA) with ESMTPSA id 1845cb15b110006e99.001 for <59135@debbugs.gnu.org> (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256); Wed, 09 Nov 2022 14:00:37 +0000 X-Zone-Loop: e27360fb0a2f010a04b89202224f9d6a1d53536a9f06 X-Originating-IP: [136.175.111.2] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=neverwas.me ; s=x; 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=1hz7YO0Bj8nK0dz9Ze7NNl0yHuxo05Jhn042/3CQ4sk=; b=jrim8onAvPeQpOqOFtEVVTiec/ vNjKFAsUXJ58+vMnqf+hu/FIlRjKwFNV9TeJn1n1VFNS8lXnFcuj4xk8/hyj3ZovwOnuubKrP45gg LaRKLWoFPYqgZZMC9SaiXCZKOS8kjfa3FikCB5PYF5hfvA/0U2hXvYyBdBiwAoNMx+qGh11Z0Ofad 6ZyoMr+pJrtikY7IazuA/GE1acjgJQ3BIvZqTqpVpAgyUkwKF4Ai9rCfiSxZZ7rr4QfOwioEBcamo cdxINLmOIyFEcpsO/kVxgO98/G/CNjRwgFiCB0NHlldCUYXvK751GNu4/ftAhRYlsWEw3S9APQREH kMFF8e3A==; In-Reply-To: (Tohiko Looka's message of "Tue, 8 Nov 2022 17:44:04 +0000") X-Authenticated-Id: masked@neverwas.me 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:247414 gmane.emacs.erc.general:1952 Archived-At: Hi Tohiko, Tohiko Looka writes: > When receiving large files with ERC-DCC I get the error > > ERC-DCC (erc-pack-int): packet too large What version of Emacs and ERC is this? If you have the command `erc-bug', please consider using it to prepare ERC bug reports in the future. > incessantly which makes Emacs unresponsive until eventually the IRC > server connection is closed. That sounds like a bug. The process should probably be killed before the error is signaled. > I believe this happens when the file size is larger than 2 or 4 GB > which does not fit in an integer. Right. Desktops were mostly 32 bits back when DCC was a thing, and the protocol reflects that. > This causes a failure when the function erc-dcc-get-filter tries to > send back the number of received bytes. > > Is there a way around this? It depends on the file sender. If they're actually verifying your reports, then you're out of luck because who's to say how reporting should proceed on either side, post-overflow? IOW, if the reporter (file receiver) wants to send 5- or 8-byte reports or wrap back around, that needs to be coordinated beforehand with the other party (the file sender). Now, there *is* a variation of the protocol that ERC doesn't officially support but that it has nevertheless partially implemented (a flavor of, anyway). Check with the sender and see if they're operating in so-called "turbo" mode (sometimes called TSEND). I've heard that some senders enable it implicitly but don't announce that fact (if they're even aware of having done so). Regardless, if ERC thinks it's in a turbo-aware conversation, it won't send reports at all. You can toggle this behavior with the -t switch starting in Emacs 29.1. See the command usage in the ;;; Commentary section in erc-dcc.el [1] and maybe some related variables further down [2]. There's also bug#54458 [3], which gave rise to that feature. Hope that helps. Thanks, J.P. [1] https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/erc/erc-dcc.el?id=1f29ee2d#n46 [2] https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/erc/erc-dcc.el?id=1f29ee2d#n979 [3] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=54458