Re: patchwork.ozlabs.org down, and e-mails not recorded

>> socket.error: [Errno 111] Connection refused > > This looks like what would happen if you tried to use pwclient when our > web server was down. This happens every now and then for very short > periods of time when we do updates to various things (including > libraries that the web server

Re: [PATCH] Fix slow Patch counting query

I have fixed up a small error where I didn't update a test and applied this to master. I'm just waiting for Travis CI to run on my repository, and then I will push it to the main repo. As this is very important to OzLabs, I will spin a 2.1-rc1 soon. Regards, Daniel Daniel Axtens

Re: [PATCH] Add validation for regular expressions

vkaba...@redhat.com writes: > From: Veronika Kabatova > > Make sure entered regexes compile before saving them. Applied, thank you. Regards, Daniel > > Signed-off-by: Veronika Kabatova > --- > Daniel, feel free to add your Reported-by. > --- >

Re: patchwork.ozlabs.org down, and e-mails not recorded

Hi Jeff, On Tue, 20 Mar 2018 15:28:46 -0700 Jeff Kirsher wrote: > > Thanks and so far it looks like it is fixed, I will continue to > monitor it though. I did notice pwclient throwing some errors, such > as: > > Traceback (most recent call last): > File

[PATCH] docker: set timezone to Australia/Canberra

The tzinfo package isn't installed in docker, which makes the default timezone UTC. This is unfortunate: the Django TZ in settings/base.py is Australia/Canberra, and having a non-UTC TZ is good for exposing faulty assumptions about what is and isn't UTC. Signed-off-by: Daniel Axtens

Re: patchwork.ozlabs.org down, and e-mails not recorded

On Tue, Mar 20, 2018 at 5:19 AM, Jeremy Kerr wrote: > Hi all, > > Good news: with the logging we had in place recently (and a fix to > correct error reporting), it looks like we've found the problem with > parsing emails from a series. This issue was recently addressed by >

Re: patchwork.ozlabs.org down, and e-mails not recorded

Hello Jeremy, On Tue, 20 Mar 2018 20:19:01 +0800, Jeremy Kerr wrote: > Good news: with the logging we had in place recently (and a fix to > correct error reporting), it looks like we've found the problem with > parsing emails from a series. This issue was recently addressed by > Daniel, so I've

Re: patchwork.ozlabs.org down, and e-mails not recorded

Hi all, Good news: with the logging we had in place recently (and a fix to correct error reporting), it looks like we've found the problem with parsing emails from a series. This issue was recently addressed by Daniel, so I've updated patchwork.ozlabs.org to run the current stable/2.0 branch,

[PATCH] parsemail: Clarify exit codes

jk reports that the patchwork error codes are really unhelpful for correct integration with an MDA. In particular they make sorting out failures into a separate queue very difficult. Make this better and clearer. Update the comment for parse_mail regarding return values and exceptions to line up