Re: Retroactive FBR: Fix mailman3 "template" scheme

2017-05-31 Thread Ricky Elrod
+1 On Wed, May 31, 2017 at 3:04 PM, Stephen John Smoogen wrote: > +1 > > On 31 May 2017 at 14:54, Patrick Uiterwijk wrote: >> Hi, >> >> While I was debugging settings not saving for Mailman, I found out >> that this was caused >> by the schema of the

Re: Retroactive FBR: Fix mailman3 "template" scheme

2017-05-31 Thread Stephen John Smoogen
+1 On 31 May 2017 at 14:54, Patrick Uiterwijk wrote: > Hi, > > While I was debugging settings not saving for Mailman, I found out > that this was caused > by the schema of the "template" table being incorrect. > > It had the following gem: > password | timestamp without

Retroactive FBR: Fix mailman3 "template" scheme

2017-05-31 Thread Patrick Uiterwijk
Hi, While I was debugging settings not saving for Mailman, I found out that this was caused by the schema of the "template" table being incorrect. It had the following gem: password | timestamp without time zone I've just ran the following query to make it be identical to what's in the code:

Re: FBR: Apply patch to FMN to resume

2017-05-31 Thread Michal Novotny
+1 On Wed, May 31, 2017 at 8:51 PM, Patrick Uiterwijk wrote: > Hi all, > > Can I get +1s to apply the patch for > https://patch-diff.githubusercontent.com/raw/fedora-infra/fedmsg_meta_ > fedora_infrastructure/pull/430.patch > on prod, so that FMN can continue running? > >

Re: FBR: Apply patch to FMN to resume

2017-05-31 Thread Stephen John Smoogen
Looks good. +1 On 31 May 2017 at 14:51, Patrick Uiterwijk wrote: > Hi all, > > Can I get +1s to apply the patch for > https://patch-diff.githubusercontent.com/raw/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/430.patch > on prod, so that FMN can continue running? > >

FBR: Apply patch to FMN to resume

2017-05-31 Thread Patrick Uiterwijk
Hi all, Can I get +1s to apply the patch for https://patch-diff.githubusercontent.com/raw/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/430.patch on prod, so that FMN can continue running? Thanks, Patrick ___ infrastructure mailing list --

FMN 1.3.0

2017-05-31 Thread Jeremy Cline
Hey all, A new version of FMN, 1.3.0, has been released and will be pushed to staging shortly so that it'll be ready when the freeze is over. The changelog is included below. 1.3.0 = Refactors - * Merge the fmn.sse repository into the fmn repository. * Merge the fmn.web repository

Re: FBR: up timeouts on kojipkgs varnish

2017-05-31 Thread Patrick Uiterwijk
+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: up timeouts on kojipkgs varnish

2017-05-31 Thread Pierre-Yves Chibon
On Wed, May 31, 2017 at 08:27:33AM -0600, Kevin Fenzi wrote: > Greetings. > > Due to issues with slow storage recently we have seen kojipkgs spike in > load and be slow to return packages to download. This makes varnish > return a 503 back to the build or compose and causes them to fail. > > We

Re: [FBR] Ignore any new architectures in Autocloud

2017-05-31 Thread Patrick Uiterwijk
+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [FBR] Ignore any new architectures in Autocloud

2017-05-31 Thread Stephen John Smoogen
Code looks clean and should not cause problems. If there are the reverse should be easy to apply. +1 On 31 May 2017 at 07:32, Sayan Chowdhury wrote: > Hi, > > Right now, Autocloud starts failing whenever a new architecture is added. > So, I have merged a PR which

[FBR] Ignore any new architectures in Autocloud

2017-05-31 Thread Sayan Chowdhury
Hi, Right now, Autocloud starts failing whenever a new architecture is added. So, I have merged a PR which would ignore any new architectures until and unless specifically mentioned. Here is the PR[1]. +1s? [1] https://github.com/kushaldas/autocloud/pull/56/files -- Sayan