discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH 0/5] New command for copying public-inbox URLs
Date: Sun, 07 Feb 2021 11:57:58 -0500
Message-ID: <877dnjzug9.fsf@kyleam.com> (raw)
In-Reply-To: <87sg6859zp.fsf@yoctocell.xyz>

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 [1].
> Are you able to reproduce this?

Just tried piem-b4-am-from-mid from an eww buffer visiting
<https://inbox.kyleam.com/piem/20210207075738.8752-1-kyle@kyleam.com>
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%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://inbox.kyleam.com/piem/20210207075738.8752-1-kyle@kyleam.com/t.mbox.gz | zless

> Sorry for the extra noise.

Not at all.  Thanks for reporting.  Sorry I don't have more helpful
response.

  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 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

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dnjzug9.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --cc=public@yoctocell.xyz \
    --subject='Re: [PATCH 0/5] New command for copying public-inbox URLs' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

discussion and development of piem

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.kyleam.com/piem/0 piem/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 piem piem/ https://inbox.kyleam.com/piem \
		piem@inbox.kyleam.com
	public-inbox-index piem

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://news.yhetil.org/yhetil.emacs.piem


code repositories for project(s) associated with this inbox:

	https://git.kyleam.com/piem/

AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git