Hi Thomas, OK, I can reproduce that.
Stephen: this is going to interact with your series on moving parsing into management commands. We're also going to need to do a different patch for the 1.1 stable branch. We might even want to go all the way back to 1.0 for kernel.org... Regards, Daniel Thomas Monjalon <thomas.monja...@6wind.com> writes: > Hi, > > 2016-09-16 08:33, Daniel Axtens: >> Hi Thomas, >> >> > Sometimes we receive some patches with a strange character in >> > a header "Received:" so the patch is not parsed in patchwork. >> > I have not yet investigated where the script is failing, >> > but I just want to ask first if there is a work in progress >> > about this issue? >> > And could it be fixed by removing "Received:" lines from the email? >> >> Python 2 or Python 3? I know about Py3 parsing issues, but not about any >> Py2 ones. > > It is Python 2.7. > >> Also, I'm collecting a set of these sorts of 'interesting' emails to >> integrate into the tests. If you could forward me a copy that would be >> very much appreciated. I don't know if it's a public mail - if not, feel >> free to redact anything sensitive. As long as it's still a valid >> email and still makes patchwork fail, it's helpful. > > It is a public email. I've just sent you one. > The problem is the character _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
