From: David Bremner <david@tethera.net>
To: "W. Trevor King" <wking@tremily.us>
Cc: notmuch@notmuchmail.org
Subject: Re: problems with nmbug and empty prefix (UnicodeWarning and broken pipe)
Date: Sat, 13 Feb 2016 22:41:40 -0400 [thread overview]
Message-ID: <87ziv4813v.fsf@zancas.localnet> (raw)
In-Reply-To: <20160213223357.GC4265@odin.tremily.us>
"W. Trevor King" <wking@tremily.us> writes:
>
> $ nmbug --log-level debug commit
>
> which will give us the full traceback.
>
Traceback (most recent call last):
File "/home/bremner/.config/scripts/nmbug.real", line 834, in <module>
args.func(**kwargs)
File "/home/bremner/.config/scripts/nmbug.real", line 324, in commit
status = get_status()
File "/home/bremner/.config/scripts/nmbug.real", line 581, in get_status
index = _index_tags()
File "/home/bremner/.config/scripts/nmbug.real", line 621, in _index_tags
git.stdin.write(line)
> We only call ‘notmuch dump …’ from _index_tags, where dump's stdout is
> tweaked and fed into ‘git update-index …’. Your urllib UnicodeWarning
> suggests the issue lies in:
>
> tags = [
> _unquote(tag[len(prefix):])
> for tag in tags_string.split()
> if tag.startswith(prefix)]
Looking at the source for urllib, that line is actually in quote, which
is called only from _hex_quote
It turns out I only have a problem with python2.7; python3.4 completes
the commit. At a guess, that suggests a unicode problem of some kind.
Unfortunately despite my best efforts with filterwarnings, I couldn't
figure out how to get a stack trace for that UnicodeWarning.
d
next prev parent reply other threads:[~2016-02-14 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 19:10 problems with nmbug and empty prefix David Bremner
2016-02-13 22:33 ` problems with nmbug and empty prefix (UnicodeWarning and broken pipe) W. Trevor King
2016-02-14 2:41 ` David Bremner [this message]
2016-02-14 6:31 ` W. Trevor King
2016-02-14 12:22 ` David Bremner
2016-02-14 22:33 ` W. Trevor King
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ziv4813v.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=wking@tremily.us \
/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
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
https://yhetil.org/notmuch.git/
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).