From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.3.4 released
Date: Wed, 25 Mar 2020 11:05:06 -0400 [thread overview]
Message-ID: <20200325150506.dgbmavaqfdjxtjc4@chatter.i7.local> (raw)
In-Reply-To: <CAHmME9o5UDKtrOJ_ffg=0avSx4poOpjbDS+rN2uZ3EBtv7_Miw@mail.gmail.com>
On Tue, Mar 24, 2020 at 08:19:00PM -0600, Jason A. Donenfeld wrote:
> I induced a crash:
>
> $ b4 am -c 20200324153624.23109-1-jiaxun.yang@flygoat.com
> Looking up https://lore.kernel.org/r/20200324153624.23109-1-jiaxun.yang@flygoat.com
> Grabbing thread from lore.kernel.org
> Reduced thread to strict matches only (138->107)
> Checking for newer revisions on https://lore.kernel.org/linux-devicetree/
> Analyzing 107 messages in the thread
> Found new series v1
> Found new series v2
> Traceback (most recent call last):
> File "/usr/lib/python-exec/python3.6/b4", line 11, in <module>
> load_entry_point('b4==0.3.4', 'console_scripts', 'b4')()
> File "/usr/lib64/python3.6/site-packages/b4/command.py", line 134, in cmd
> cmdargs.func(cmdargs)
> File "/usr/lib64/python3.6/site-packages/b4/command.py", line 40, in cmd_am
> b4.mbox.main(cmdargs)
> File "/usr/lib64/python3.6/site-packages/b4/mbox.py", line 407, in main
> mbox_to_am(threadmbox, config, cmdargs)
> File "/usr/lib64/python3.6/site-packages/b4/mbox.py", line 114, in mbox_to_am
> lmbx.add_message(msg)
> File "/usr/lib64/python3.6/site-packages/b4/__init__.py", line 232,
> in add_message
> lmsg = LoreMessage(msg)
> File "/usr/lib64/python3.6/site-packages/b4/__init__.py", line 572, in __init__
> if diffstatre.search(self.body):
> TypeError: expected string or bytes-like object
Thanks for the report -- the latest commit no longer breaks on messages
containing no usable text/plain parts (that message is html-only).
I'll release 0.3.5 in the near future to fix this and a few other bugs.
-K
next prev parent reply other threads:[~2020-03-25 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 22:20 b4 v0.3.4 released Konstantin Ryabitsev
2020-03-25 2:11 ` [kernel.org users] " Jason A. Donenfeld
2020-03-25 2:19 ` Jason A. Donenfeld
2020-03-25 15:05 ` Konstantin Ryabitsev [this message]
2020-03-25 15:26 ` Konstantin Ryabitsev
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11 ` Rob Herring
2020-03-26 16:16 ` Konstantin Ryabitsev
2020-03-26 16:27 ` James Bottomley
2020-03-26 16:31 ` Geert Uytterhoeven
[not found] ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32 ` Konstantin Ryabitsev
2020-03-26 20:18 ` Jason A. Donenfeld
2020-03-27 18:15 ` Konstantin Ryabitsev
2020-04-06 21:53 ` Konstantin Ryabitsev
2020-09-22 22:17 ` Rob Herring
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200325150506.dgbmavaqfdjxtjc4@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.org \
/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.
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 NNTP newsgroup(s).