From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:863f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms12 with LMTPS id YKt8NhocIGDuTwAAsNZ9tg (envelope-from ) for ; Sun, 07 Feb 2021 16:58:02 +0000 Received: from out1.migadu.com ([2001:41d0:2:863f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id iFTNHhgcIGBiCAAAB5/wlQ (envelope-from ) for ; Sun, 07 Feb 2021 16:58:00 +0000 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1612717080; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=y0cvqkgjT5ND52yqoPQvN801DCv9sIfvS0ASqiEoEPk=; b=fw1+JqkrKKFpC83VUlhANwhi/2VsRLCbY0C5/DwTcuZMw/D2+eOEqzZAF3Viq0z5FfU36J MbhKFB2mcasjz2rNYO/BQF1DsFE3bYtYfff10I+RibDScjLMO/ChNnTTdymnqDlQ7Ta3Qe 7D5W9AsA5ctFQkcnxtniFAVccifHH2TT3uptRTGUFEo5bazhP4pw3Lm04KayqMHzwCZJsr aMOiYZ0qPkXqrILDa9UUUcXA/xwOBKrBkgDKVvsjHfJUZn8P2/or9F47kdPt/oYQumCfbq JXt69/9alUVX+zH7TstlE9/B9F4EA/kdo88aUSplHG/ixKM91c33nU5JAXX7DQ== From: Kyle Meyer To: Xinglu Chen Cc: piem@inbox.kyleam.com Subject: Re: [PATCH 0/5] New command for copying public-inbox URLs In-Reply-To: <87sg6859zp.fsf@yoctocell.xyz> References: <20210207075738.8752-1-kyle@kyleam.com> <87sg6859zp.fsf@yoctocell.xyz> Date: Sun, 07 Feb 2021 11:57:58 -0500 Message-ID: <877dnjzug9.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyle@kyleam.com X-TUID: d6SBORhmY8cS Xinglu Chen writes: > This looks good to me. But when I try to apply the patchset with > `piem-b4-am-from-mid` it returns an error (I only pasted the last part): > > File "/nix/store/c3rw242zljng83r21jbpczwg54g97d5l-python3.8-dnspython= -2.0.0/lib/python3.8/site-packages/dns/resolver.py", line 598, in next_name= server > raise NoNameservers(request=3Dself.request, errors=3Dself.errors) > dns.resolver.NoNameservers: All nameservers failed to answer the query = key1._domainkey.kyleam.com. IN TXT: Server 192.168.1.1 UDP port 53 answered= ; Server 192.168.1.1 TCP port 53 answered [Errno 111] Connection refused > > This doesn=E2=80=99t happen if i try the same thing on the notmuch archiv= e [1]. > Are you able to reproduce this? Just tried piem-b4-am-from-mid from an eww buffer visiting and didn't run into any issues on my end. Hmm, based on dnspython being involved, I guess this happens when b4 tries to download the thread. piem-b4--get-am-files should take care of downloading the mbox (mostly to prevent users from needing to configure b4.midmask), but I guess it falls back to b4 because piem-b4--get-am-files's call to piem-download-and-decompress fails for the same reason. Anyway, going through b4 doesn't explain the above error of course, and things look okay using `b4 am' directly on my end: # in piem repo $ git config b4.midmask https://inbox.kyleam.com/piem/%s $ b4 am 20210207075738.8752-1-kyle@kyleam.com Looking up https://inbox.kyleam.com/piem/20210207075738.8752-1-kyle%40kyl= eam.com Grabbing thread from inbox.kyleam.com/piem Analyzing 7 messages in the thread [...] Assuming the above isn't a transient error, I'm guessing a plain curl call fails on your end too? $ curl -fsS \ https://inbox.kyleam.com/piem/20210207075738.8752-1-kyle@kyleam.com/t.m= box.gz | zless > Sorry for the extra noise. Not at all. Thanks for reporting. Sorry I don't have more helpful response.