From: Thomas Perrot <thomas.perrot@bootlin.com>
To: yocto@lists.yoctoproject.org, Gyorgy Sarvari <skandigraun@gmail.com>
Cc: thomas.perrot@bootlin.com
Subject: Re: [yocto] Reseive a HTTP Error 500 when send error report
Date: Wed, 16 Apr 2025 15:28:39 +0200 [thread overview]
Message-ID: <9be005368fbce86de50cb308656f2217a1b0b9dc.camel@bootlin.com> (raw)
In-Reply-To: <1836CBB1B501AE62.22324@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
Hello Gyorgi,
On Wed, 2025-04-16 at 14:17 +0200, Thomas Perrot via
lists.yoctoproject.org wrote:
> Hello Gyorgi,
>
> On Wed, 2025-04-16 at 13:22 +0200, Gyorgy Sarvari wrote:
> > Rendering[1] the error message shows a bit more details. The error
> > seems
> > to come from here[2].
> >
> > 1. You could send a patch to fix the error (I think nowadays it
> > should
> > be "urllib.parse.unquote_plus"), and wait till it's deployed
> >
>
> I believe I could.
I submitted a patch:
https://lore.kernel.org/all/20250416131828.441127-1-thomas.perrot@bootlin.com/
>
> > 2. It's a guess: have you changed the "version" attribute of the
> > send-error-script? The error indicates that the user agent is
> > "send-error-report/0.4", which seems to trigger the outdated
> > codepath,
> > and the user-agent is composed using the version variable of this
> > script, which is 0.3, in master-next too[3].
>
> The user agent is 'send-error/report/0.4' because I applied the
> following patch on top of the master branch to figure out the
> error:
> https://lore.kernel.org/all/20250416100149.274800-1-thomas.perrot@bootlin.com
> /
>
Following the log when the version is 0.3:
https://termbin.com/8fy1
Kind regards,
Thomas Perrot
> Kind regards,
> Thomas Perrot
>
> >
> > [1]: https://sarvari.me/deleteme.html (temporary link)
> >
> > [2]:
> > https://git.yoctoproject.org/error-report-web/tree/Post/views.py#n60
> >
> > [3]:
> > https://git.openembedded.org/openembedded-core/tree/scripts/send-error-report?h=master-next#n25
> >
> > On 4/16/25 12:14, Thomas Perrot via lists.yoctoproject.org wrote:
> > > Hello,
> > >
> > > I would like to share the results of my CI jobs, so I am trying
> > > to
> > > send
> > > error reports using the send-error-report command, but they are
> > > receiving an HTTP Error 500:
> > > https://termbin.com/pq28
> > >
> > > Could you please advise me on how to resolve this issue?
> > >
> > > Kind regards,
> > > Thomas Perrot
> > >
> > >
> > >
> > >
>
--
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-04-16 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 10:14 Reseive a HTTP Error 500 when send error report Thomas Perrot
2025-04-16 11:22 ` [yocto] " Gyorgy Sarvari
2025-04-16 12:17 ` Thomas Perrot
[not found] ` <1836CBB1B501AE62.22324@lists.yoctoproject.org>
2025-04-16 13:28 ` Thomas Perrot [this message]
2025-04-16 13:46 ` Gyorgy Sarvari
[not found] ` <1836C8AE53127E24.22324@lists.yoctoproject.org>
2025-04-16 11:34 ` Gyorgy Sarvari
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=9be005368fbce86de50cb308656f2217a1b0b9dc.camel@bootlin.com \
--to=thomas.perrot@bootlin.com \
--cc=skandigraun@gmail.com \
--cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.