From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: [BUG] b4: AttributeError: 'LoreAttestation' object has no attribute 'attid'
Date: Mon, 26 Oct 2020 15:49:39 -0400 [thread overview]
Message-ID: <20201026194939.r7dsx43zhd5xjebj@chatter.i7.local> (raw)
In-Reply-To: <20201026175618.GB2449445@kernel.org>
On Mon, Oct 26, 2020 at 02:56:18PM -0300, Arnaldo Carvalho de Melo wrote:
>
> [acme@five perf]$ b4 am -tcsl 20201024025918.453431-1-namhyung@kernel.org
> Looking up https://lore.kernel.org/r/20201024025918.453431-1-namhyung%40kernel.org
Note -- that thread is kinda broken because there is a [PATCH 1/2] with
no [PATCH 2/2], and we don't count [PATCH v2 2/2], as it's a different
series.
> Grabbing thread from lore.kernel.org/lkml
> Checking for newer revisions on https://lore.kernel.org/lkml/
> Analyzing 8 messages in the thread
> ---
> Thread incomplete, attempting to backfill
> Traceback (most recent call last):
> File "/home/acme/git/b4/b4/command.py", line 238, in <module>
> cmd()
> File "/home/acme/git/b4/b4/command.py", line 221, in cmd
> cmdargs.func(cmdargs)
> File "/home/acme/git/b4/b4/command.py", line 40, in cmd_am
> b4.mbox.main(cmdargs)
> File "/home/acme/git/b4/b4/mbox.py", line 509, in main
> mbox_to_am(threadmbox, cmdargs)
> File "/home/acme/git/b4/b4/mbox.py", line 49, in mbox_to_am
> lser = lmbx.get_series(revision=wantver, sloppytrailers=cmdargs.sloppytrailers)
> File "/home/acme/git/b4/b4/__init__.py", line 307, in get_series
> attid = pmsg.attestation.attid
> AttributeError: 'LoreAttestation' object has no attribute 'attid'
There is a fix for this in the current master, though new attestation
code is a bit mid-flight and may cause occasional further problems until
I complete it.
Thanks for the report!
-K
parent reply other threads:[~2020-10-26 19:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201026175618.GB2449445@kernel.org>]
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=20201026194939.r7dsx43zhd5xjebj@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=acme@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;
as well as URLs for NNTP newsgroup(s).