From: Kyle Meyer <firstname.lastname@example.org>
To: Xinglu Chen <email@example.com>
Subject: Re: [PATCH 0/5] New command for copying public-inbox URLs
Date: Sun, 07 Feb 2021 11:57:58 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
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_nameserver
> raise NoNameservers(request=self.request, errors=self.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’t happen if i try the same thing on the notmuch archive .
> 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 email@example.com
Looking up https://inbox.kyleam.com/piem/20210207075738.8752-1-kyle%40kyleam.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://firstname.lastname@example.org/t.mbox.gz | zless
> Sorry for the extra noise.
Not at all. Thanks for reporting. Sorry I don't have more helpful
next prev parent reply other threads:[~2021-02-07 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 7:57 [PATCH 0/5] New command for copying public-inbox URLs Kyle Meyer
2021-02-07 7:57 ` [PATCH 1/5] piem: Add helper to construct message ID link Kyle Meyer
2021-02-07 7:57 ` [PATCH 2/5] piem-dispatch: Add command for copying public-inbox URLs Kyle Meyer
2021-02-07 7:57 ` [PATCH 3/5] piem-copy-mid-url: Add support for browsing url Kyle Meyer
2021-02-07 7:57 ` [PATCH 4/5] piem-copy-mid-url: Allow overriding browse-url-browser-function Kyle Meyer
2021-02-07 7:57 ` [PATCH 5/5] manual: Add section on "copy public-inbox link" functionality Kyle Meyer
2021-02-07 12:38 ` [PATCH 0/5] New command for copying public-inbox URLs Xinglu Chen
2021-02-07 16:57 ` Kyle Meyer [this message]
2021-02-07 17:35 ` Kyle Meyer
2021-02-07 20:25 ` Xinglu Chen
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:
List information: https://git.kyleam.com/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).