| Summary: | Pushing recent OE-Core changes gave patchwork traceback | ||
|---|---|---|---|
| Product: | [Infrastructure] Infrastructure General | Reporter: | Richard Purdie <richard.purdie> |
| Component: | infrastructure-general | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | mhalstead, randy.macleod |
| Version: | unspecified | ||
| Target Milestone: | 4.0 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2019-12-04 12:35:55 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? 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. @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. Any news? Michael. The infrastructure have changed with regard to this and it isn't been seen in a long time. Mark as obsolete. |