From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: tools@kernel.org
Subject: Re: [b4] CRITICAL: prep-pre-flight-checks must be a list, got str
Date: Wed, 11 Jun 2025 11:07:25 -0400 [thread overview]
Message-ID: <20250611-bizarre-granite-mastodon-de6b32@lemur> (raw)
In-Reply-To: <20250610194624.GA1933519@ax162>
On Tue, Jun 10, 2025 at 12:46:24PM -0700, Nathan Chancellor wrote:
> After commit 8cae108 ("Further mypy typing enhancements"), I am seeing
> an error when running 'b4 send':
>
> $ b4 send
> Converted the branch to 1 messages
> CRITICAL: prep-pre-flight-checks must be a list, got str
Thank you for the report. I didn't take the patch, because the way this was
implemented needed to be redone anyway. Please check the latest master, and
thank you for trying out the bleeding edge!
-K
prev parent reply other threads:[~2025-06-11 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 19:46 [b4] CRITICAL: prep-pre-flight-checks must be a list, got str Nathan Chancellor
2025-06-11 15:07 ` Konstantin Ryabitsev [this message]
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=20250611-bizarre-granite-mastodon-de6b32@lemur \
--to=konstantin@linuxfoundation.org \
--cc=nathan@kernel.org \
--cc=tools@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