From: Michael Wood <michael.g.wood@intel.com>
To: mariano.lopez@linux.intel.com, yocto@yoctoproject.org
Subject: Re: [error-report-web][PATCH] parser: Add Unicode support to the error log
Date: Wed, 30 Sep 2015 15:31:40 +0100 [thread overview]
Message-ID: <560BF24C.6070309@intel.com> (raw)
In-Reply-To: <1443621262-322-1-git-send-email-mariano.lopez@linux.intel.com>
On 30/09/15 14:54, mariano.lopez@linux.intel.com wrote:
> From: Mariano Lopez <mariano.lopez@linux.intel.com>
>
> If the server receives a error log with Unicode
> character in it, it will throw and internal server
> error, this is caused because the server doesn't
> try to convert everything to ASCII
>
> This patch changes the log encoding to UTF-8 so
> it will allow Unicode characters.
>
> [YOCTO #8225]
>
> Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
> ---
> Post/parser.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Post/parser.py b/Post/parser.py
> index d33a968..599afde 100644
> --- a/Post/parser.py
> +++ b/Post/parser.py
> @@ -85,7 +85,7 @@ class Parser:
> recipe = package
> recipe_version = "unknown"
>
> - f = BuildFailure(TASK = str(fail['task']), RECIPE = recipe, RECIPE_VERSION = recipe_version, ERROR_DETAILS = str(fail['log']), BUILD = b)
> + f = BuildFailure(TASK = str(fail['task']), RECIPE = recipe, RECIPE_VERSION = recipe_version, ERROR_DETAILS = fail['log'].encode('utf-8'), BUILD = b)
>
> f.save()
>
Thanks for the patch. Now committed.
Michael
prev parent reply other threads:[~2015-09-30 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:54 [error-report-web][PATCH] parser: Add Unicode support to the error log mariano.lopez
2015-09-30 14:31 ` Michael Wood [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=560BF24C.6070309@intel.com \
--to=michael.g.wood@intel.com \
--cc=mariano.lopez@linux.intel.com \
--cc=yocto@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.