From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: tools@linux.kernel.org
Subject: Error using b4 web endpoint (was Re: git send-email friendly smtp provider anyone?)
Date: Tue, 22 Nov 2022 14:44:28 -0500 [thread overview]
Message-ID: <20221122194428.fmbayuz6vbvdd6uw@meerkat.local> (raw)
In-Reply-To: <02bc2442-e3b3-d720-9d13-ffcdfd760fb8@tronnes.org>
(Dropping everyone from cc's and adding the tools list.)
On Tue, Nov 22, 2022 at 08:22:22PM +0100, Noralf Trønnes wrote:
> > Yes. There will be a 0.10.2 in the near future, but the incoming fixes
> > shouldn't make much difference for the b4 send code.
> >
>
> This is what I got:
>
> $ b4 send --web-auth-verify <challenge string from email>
> Signing challenge
> Submitting verification to https://lkml.kernel.org/_b4_submit
> Traceback (most recent call last):
> File "/home/pi/.local/lib/python3.10/site-packages/b4/ez.py", line 188, in auth_verify
> res = ses.post(endpoint, json=req)
> ...
> TypeError: Object of type bytes is not JSON serializable
This is very strange, because this is literally the code in question:
req = {
'action': 'auth-verify',
'msg': bdata.encode(),
}
logger.info('Submitting verification to %s', endpoint)
ses = b4.get_requests_session()
res = ses.post(endpoint, json=req)
I don't see where "Object of type bytes" would come from. Can you possibly
insert the following above the `res = ses.post` line:
logger.debug('endpoint=%s, req=%s', endpoint, req)
Regards,
-K
next parent reply other threads:[~2022-11-22 19:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1bc45775-0667-01f8-36e1-9f65d3081092@tronnes.org>
[not found] ` <20221121151922.jaal6ym7z2ejju4q@houat>
[not found] ` <de12952f-8346-8995-236d-69dcb70f19f6@tronnes.org>
[not found] ` <20221122155122.edxtmsqpjxgj4dsj@meerkat.local>
[not found] ` <3b06dfd5-0eb4-dbfc-6ba8-077b1a92865b@tronnes.org>
[not found] ` <20221122185001.q6hmeblp64jqdzvz@meerkat.local>
[not found] ` <02bc2442-e3b3-d720-9d13-ffcdfd760fb8@tronnes.org>
2022-11-22 19:44 ` Konstantin Ryabitsev [this message]
2022-11-22 19:48 ` Error using b4 web endpoint (was Re: git send-email friendly smtp provider anyone?) Noralf Trønnes
2022-11-22 20:00 ` Konstantin Ryabitsev
2022-11-22 20:10 ` Noralf Trønnes
2022-11-22 20:20 ` Konstantin Ryabitsev
2022-11-22 20:26 ` Noralf Trønnes
2022-11-22 20:44 ` Konstantin Ryabitsev
2022-11-22 21:03 ` Noralf Trønnes
2022-11-22 21:14 ` Konstantin Ryabitsev
2022-11-22 22:05 ` Konstantin Ryabitsev
2022-11-30 16:17 ` Noralf Trønnes
2022-11-30 16:55 ` Konstantin Ryabitsev
2022-11-30 17:02 ` Noralf Trønnes
2022-11-30 19:17 ` Konstantin Ryabitsev
2022-11-30 19:34 ` Noralf Trønnes
2022-11-30 19:39 ` Konstantin Ryabitsev
2022-11-30 19:59 ` Noralf Trønnes
2022-12-01 14:42 ` Konstantin Ryabitsev
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=20221122194428.fmbayuz6vbvdd6uw@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=noralf@tronnes.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 read-only IMAP folder(s) and NNTP newsgroup(s).