Re: [Patchwork-maintainers] patchwork.ozlabs.org downtime for maintenance - 15/16 August
Hi all, On Thu, 18 Jan 2024 00:36:39 +0800 Jeremy Kerr wrote: > > > When and how long do those run? I'm pretty much working your > > overnight. > > I'd have to defer to Stephen on that, but I had been assuming 4am / > 17:00 UTC. Yeah, 4am to 6am our time (currently +1100) ... it takes a long time to backup a 25GB database :-( We may need to consider alternative backup methods? See https://munin.ozlabs.org/ozlabs.org/legolas.ozlabs.org/index.html (legolas is patchwork.ozlabs.org). -- Cheers, Stephen Rothwell pgpQQHbHCn8Er.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Downloading archives no longer possible
Hi Jeremy, On Wed, 03 Jun 2020 09:03:10 +0800 Jeremy Kerr wrote: > > > Our documentation [1] suggests people initialize their development > > environments by download the archives of the Patchwork mailing lists > > from [2] and load them with the 'parsearchive' command. However, it's > > been pointed out to me that at request to [1] now return only a handful > > of recent messages. Is this change intentional? > > No, no intentional change there; that's just something exported by > mailman, I'm not sure how it's managed. > > sfr: has anything changed on the mailman side there? No, not reaally. :-) I regularly rotate and compress that file ... and I am suprised to learn that it is (meant to be) directly accessible. Oh, well, I have recombined the rotations into the above file, so it should work again. -- Cheers, Stephen Rothwell pgpPCr6rAHpLe.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes
On Fri, 11 Oct 2019 10:16:40 +1100 Daniel Axtens wrote: > > Andrew Donnellan writes: > > > On 11/10/19 6:41 am, Jonathan Nieder wrote: > >> Interesting! I'm cc-ing the Git mailing list in case "git am" might > >> wnat to learn the same support. > > Argh, that reminds me... this patch only rewrites the name and email > > that is recorded as the Patchwork submitter, it doesn't actually rewrite > > the From: header when you fetch the mbox off Patchwork. > > > > Part of me would really like to keep Patchwork mboxes as close as > > possible to the mbox we ingested, but on the other hand it means the > > mangled address is still going to land in the git repo at the end... so > > I should probably just change it? > > Yes, I think change it. If you're worried, stash the original one in the > headers. Or add a From: line to the start of the body (if one is not already there). -- Cheers, Stephen Rothwell pgpATtDfG0Tsi.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: ozlabs.org down?
Hi all, On Mon, 03 Sep 2018 13:43:13 -0700 (PDT) David Miller wrote: > > From: Richard Weinberger > Date: Mon, 3 Sep 2018 22:22:09 +0200 > > > The site seems to be unreachable again. At least here in Europe. :-( > > It is unreachable for me as well, and has been since this morning PST > timezone. Yeah, we were off the net from about 2:30am to 6:45am +1000. Looks like I need to have another chat with our hosting company :-( -- Cheers, Stephen Rothwell pgpq3a1vp96ss.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: ozlabs.org down?
Hi all, On Wed, 22 Aug 2018 16:12:44 -0700 Randy Dunlap wrote: > > On 08/22/2018 04:04 PM, Andrew Donnellan wrote: > > On 23/08/18 02:12, Jeff Kirsher wrote: > >> It appears the entire site is down, including patchworks. Is this > >> expected? And for how long? > > > > + sfr > > > > It appears up for me right now. > > > > We've had a few dropouts over the last few weeks as a result of the > > upstream ISP having connectivity issues - it's possible that we've just hit > > that again. > > > > I checked a few hours ago and it was down, but it's been up for over one hour > now for me. It hasn't actually been down for over 140 days, but our hosting company has been having trouble with the router we are connected to and replaced it a few days ago. I have no idea what happened this morning, I will see if I can find out if these intermittent interruptions are going to continue. :-( -- Cheers, Stephen Rothwell pgpNB0U774kai.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: patchwork.ozlabs.org down, and e-mails not recorded
Hi Jeff, On Tue, 20 Mar 2018 15:28:46 -0700 Jeff Kirsher <jeffrey.t.kirs...@intel.com> 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 "/home/jtkirshe/bin/pwclient", line 827, in > main() > File "/home/jtkirshe/bin/pwclient", line 780, in main > action_get(rpc, patch_id) > File "/home/jtkirshe/bin/pwclient", line 300, in action_get > patch = rpc.patch_get(patch_id) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1243, in __call__ > return self.__send(self.__name, args) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1602, in __request > verbose=self.__verbose > File "/usr/lib64/python2.7/xmlrpclib.py", line 1283, in request > return self.single_request(host, handler, request_body, verbose) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1311, in single_request > self.send_content(h, request_body) > File "/usr/lib64/python2.7/xmlrpclib.py", line 1459, in send_content > connection.endheaders(request_body) > File "/usr/lib64/python2.7/httplib.py", line 1038, in endheaders > self._send_output(message_body) > File "/usr/lib64/python2.7/httplib.py", line 882, in _send_output > self.send(msg) > File "/usr/lib64/python2.7/httplib.py", line 844, in send > self.connect() > File "/usr/lib64/python2.7/httplib.py", line 821, in connect > self.timeout, self.source_address) > File "/usr/lib64/python2.7/socket.py", line 575, in create_connection > raise err > 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 itself depends on). Do the developers: maybe it is worth catching this error in particular and giving some reasonable message (or, optionally,trying again after a short wait - or both). -- Cheers, Stephen Rothwell pgpHhR5yOOflo.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: patchwork.ozlabs.org down, and e-mails not recorded
Hi all, On Sat, 10 Mar 2018 12:58:06 +0100 Peter Korsgaard <pe...@korsgaard.com> wrote: > > Any news on this? We still see missing mails, and I even received a > temporary bounce from the patchwork addres this morning: > > > This is the mail system at host ozlabs.org. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > >The mail system > > <patchwork-incoming-buildr...@bilbo.ozlabs.org> (expanded from > <incoming-buildr...@patchwork.ozlabs.org>): temporary failure We have quite a few of these sitting in our queue :-( I have extended the maximum time a mail can sit in the queue before it is rejected to 12 days, so please see if you can figure out why these mails are being TEMPFAILed before then (otherwise more mails may be lost to patchwork). -- Cheers, Stephen Rothwell pgp5qOGwnyyes.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: patchwork.ozlabs.org down, and e-mails not recorded
Hi Andrew, On Sat, 17 Feb 2018 14:29:04 +1100 Andrew Donnellan <andrew.donnel...@au1.ibm.com> wrote: > > On 17/02/18 01:49, Thomas Petazzoni wrote: > > Thanks a lot for the follow-up details on this. > > > > I think it's worth mentioning that it seems to be a relatively "recent" > > regression, probably within the last 6 months or so. In the past, we > > were clearly not seeing such a problem, and all patches were properly > > recorded. The problem is frequent enough that we would have noticed. > > We have, anecdotally, noticed some regressions in database performance > in patchwork 2.0 which might increase the likelihood of hitting race > conditions. Hmm. Not to mention the load problems we have on ozlabs.org ... -- Cheers, Stephen Rothwell pgpS77wPinXl_.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: [PATCH] RFC: Monkey-patch Django performance bug
Hi Stephen, On Thu, 07 Sep 2017 19:41:36 +0100 Stephen Finucane <step...@that.guru> wrote: > > What version of Django is the Ozlabs instance using? Would it be possible to > work with the upstream Django folks to get this backported to those versions? > If nothing else, this patch is there and I'd be OK to add a pointer in the > docs > about it. I just don't want to merge it in Patchwork, heh. Ozlabs.org is currently running v1.10.7 of Django. The latest version available is in Debian is v1.11.4 (for testing that ozlabs.org runs) or v1.11.5 for unstable (which will be in testing soon). However, Patchwork is only documented to support v1.10 (as far as I know). -- Cheers, Stephen Rothwell ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Adding Django 1.8 + Python 3 support
Hi Stephen, On Tue, 7 Apr 2015 22:39:07 +0100 Stephen Finucane stephenfinuc...@hotmail.com wrote: As mentioned in the cover letter for same, patchwork support two now-deprecated versions of Django (1.5, 1.6). On the other hand, it does not yet support 1.8, which is the latest LTS version of Django. While it would be irresponsible to drop support for two versions of Django in a short time span, I suggest dropping support for version 1.5 followed by adding of support for 1.8. However, I have little to no say in this of course :) Similarly, Python 2.7 is now approaching five years and Python 3 has developed and grown in popularity during that time. The addition of Python 3 support is probably a good idea at this point. I've begun looking into this but it's going to be a lot of work and I'd like to know if there's demand for patches before beginning anything. I think the addition of tox should make testing of this a cinch. I suggest dropping support for Python 2.7 (I'm unsure if 2.6 support is still expected (Django 1.7 doesn't support it) and I can't test it on Fedora 21) and adding support for Python 3.0 at the very minimum. What are people's opinions on the? Is there a roadmap anywhere that I should look at? Just a data point: Debian Stable (Wheezy) has python-django version 1.4.5, whereas Testing (Jessie) (which will become Stable soon(?)) has 1.7.7. So Stable is already unsupported by patchwork. Debian Stable has python version 2.7.3 and python3 version 3.2.3, while Testing has 2.7.9 and 3.4.2 respectively. Its probably also worth considering what is in the latest Ubuntu LTS, RHEL and SLES releases. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpEzbM9KWX5p.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: [PATCH] pwclient: honor PAGER for view
Hi Bernhard, On Mon, 2 Mar 2015 16:18:34 +0100 Bernhard Reutner-Fischer rep.dot@gmail.com wrote: Use the PAGER of the environment to view patches It would be nice if PAGER was not used when stdout is not a terminal so that piping the output works naturally. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpgj0Vj5fh6x.pgp Description: OpenPGP digital signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Postgresql update
Hi all, On Tue, 12 Aug 2014 09:42:49 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: I am going to update Postgresql to version 9.3 (from 9.1) today at about 11:00 (Canberra time - in about an 80 minutes). This will mean that the databases are unavailable for some amount of time as they will all be dumped and reloaded. This will take an unspecified amount of time since the patchwork database is quite large (!). Other main things affected will be Roundcube and kisskb. Sorry for the inconvenience. All done. It seems to have gone without a hitch. -- Cheers, Stephen Rothwells...@canb.auug.org.au signature.asc Description: PGP signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
Re: Patchwork on ozlabs.org is down
Hi, On Tue, 10 Dec 2013 20:57:09 +0100 Yann E. MORIN yann.morin.1...@free.fr wrote: Just to let you know that patchwork.ozlabs.org is down (and ozlabs.org too). Yeah, ozlabs.org crashed last night. It should be up again now. -- Cheers, Stephen Rothwells...@canb.auug.org.au pgpIBbOOKzSw_.pgp Description: PGP signature ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
