From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: "b4 ty -d all" crash
Date: Mon, 17 Oct 2022 16:22:14 -0400 [thread overview]
Message-ID: <20221017202214.dyt7lokid4shpqsv@nitro.local> (raw)
In-Reply-To: <20221017172323.GA3715117@bhelgaas>
On Mon, Oct 17, 2022 at 12:23:23PM -0500, Bjorn Helgaas wrote:
> I've used "b4 am" for a long time, but I'm a first-time and naive
> "b4 ty" user:
>
> 12:17:52 ~/linux (for-linus)$ b4 ty -d all
> Discarding 707 messages
Oh my.
> Discarded: [PATCH 0/5] Handled return value of platform_get_irq correctly
> Traceback (most recent call last):
> File "/home/bjorn/.local/bin/b4", line 8, in <module>
> sys.exit(cmd())
> File "/home/bjorn/.local/lib/python3.8/site-packages/b4/command.py", line 341, in cmd
> cmdargs.func(cmdargs)
> File "/home/bjorn/.local/lib/python3.8/site-packages/b4/command.py", line 106, in cmd_ty
> b4.ty.main(cmdargs)
> File "/home/bjorn/.local/lib/python3.8/site-packages/b4/ty.py", line 678, in main
> discard_selected(cmdargs)
> File "/home/bjorn/.local/lib/python3.8/site-packages/b4/ty.py", line 578, in discard_selected
> msgids.append(pdata[2])
> IndexError: list index out of range
I think it's most likely due to tracking file format changes between when this
feature was first introduced and subsequent changes, especially considering
that your first tracked series are from:
> Date: Mon, 4 May 2020 07:18:10 +0200
I suggest you just delete them manually by going into ~/.local/share/b4 and
deleting all *.am files.
-K
next prev parent reply other threads:[~2022-10-17 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 17:23 "b4 ty -d all" crash Bjorn Helgaas
2022-10-17 20:22 ` Konstantin Ryabitsev [this message]
2022-10-17 21:22 ` Bjorn Helgaas
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=20221017202214.dyt7lokid4shpqsv@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=tools@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