Bug 13672 - Pushing recent OE-Core changes gave patchwork traceback
Summary: Pushing recent OE-Core changes gave patchwork traceback
Status: RESOLVED OBSOLETE
Alias: None
Product: Infrastructure General
Classification: Infrastructure
Component: infrastructure-general (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 4.0 M3
Assignee: Michael Halstead
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-12-04 12:35 UTC by Richard Purdie
Modified: 2022-02-20 16:07 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Purdie 2019-12-04 12:35:55 UTC
To ssh://push.yoctoproject.org/poky.git
 + 0161d2ff259...1da86d641a7 master-next -> master-next (forced update)
Enumerating objects: 223, done.
Counting objects: 100% (223/223), done.
Delta compression using up to 8 threads
Compressing objects: 100% (160/160), done.
Writing objects: 100% (162/162), 291.55 KiB | 3.99 MiB/s, done.
Total 162 (delta 108), reused 0 (delta 0)
To ssh://push.yoctoproject.org/poky-contrib.git
   1fb4aa42f9c..dbcd6b6e7a5  master -> master
Enumerating objects: 223, done.
Counting objects: 100% (223/223), done.
Delta compression using up to 8 threads
Compressing objects: 100% (100/100), done.
Writing objects: 100% (162/162), 290.56 KiB | 48.43 MiB/s, done.
Total 162 (delta 111), reused 94 (delta 60)
remote: Sending notification emails to: openembedded-commits@lists.openembedded.org
remote: Traceback (most recent call last):
remote:   File "/usr/local/patchwork/patchwork/parser.py", line 312, in <module>
remote:     sys.exit(main(sys.argv))
remote:   File "/usr/local/patchwork/patchwork/parser.py", line 293, in main
remote:     content = sys.stdin.read().decode('utf-8')
remote:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
remote:     return codecs.utf_8_decode(input, errors, True)
remote: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe5 in position 728340: invalid continuation byte
To ssh://git.openembedded.org/openembedded-core
   ddd2c562440..afb8d456360  master -> master
Enumerating objects: 48, done.
Counting objects: 100% (48/48), done.
Delta compression using up to 8 threads
Compressing objects: 100% (21/21), done.
Writing objects: 100% (30/30), 2.71 KiB | 1.35 MiB/s, done.
Total 30 (delta 25), reused 9 (delta 9)
remote: Sending notification emails to: openembedded-commits@lists.openembedded.org
remote: Traceback (most recent call last):
remote:   File "/usr/local/patchwork/patchwork/parser.py", line 312, in <module>
remote:     sys.exit(main(sys.argv))
remote:   File "/usr/local/patchwork/patchwork/parser.py", line 293, in main
remote:     content = sys.stdin.read().decode('utf-8')
remote:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
remote:     return codecs.utf_8_decode(input, errors, True)
remote: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe5 in position 728340: invalid continuation byte
To ssh://git.openembedded.org/openembedded-core
 + a9ebb9002d5...e4da8c52143 master-next -> master-next (forced update)
Comment 1 Michael Halstead 2019-12-10 20:58:24 UTC
It appears http://git.yoctoproject.org/cgit.cgi/patchwork/tree/patchwork/parser.py?id=c64dfc9a6042beb57652e38ccb73bbae8b1e5012#n293 is having trouble with å but I don't see that character anywhere in the commit.

What do you think about adding something like unicode(str, errors='ignore') to strip out any weirdness?
Comment 2 Changqing Li 2019-12-11 05:57:55 UTC
I did below test:

insert å  into test.mbox with vim, and run parse.py -p < test.mbox

and parse.py works well, no traceback. 

I don't know how to input a not work 'å' into test.mbox by vim.

I also suspect we can just ignore the error as Michael saied.
Comment 3 Changqing Li 2019-12-17 07:11:08 UTC
@Michael, could you fix this problem? I can't see which commit cause this problem. It is better you test with "that commit" after fix the problem.


or you can reassigned to me and attached "that commit" caused this problem.
Comment 4 Randy MacLeod 2020-01-16 15:55:42 UTC
Any news?
Comment 5 Randy MacLeod 2020-02-20 16:07:25 UTC
Michael.
Comment 6 Richard Purdie 2022-02-20 16:07:35 UTC
The infrastructure have changed with regard to this and it isn't been seen in a long time. Mark as obsolete.