Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gj2lm-0007M8-A1 for pgsql-www@arkaria.postgresql.org; Mon, 14 Jan 2019 13:59:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gj2lk-0006R4-QH for pgsql-www@arkaria.postgresql.org; Mon, 14 Jan 2019 13:59:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gj2lk-0006Qr-Bt for pgsql-www@lists.postgresql.org; Mon, 14 Jan 2019 13:59:12 +0000 Received: from mail-lf1-x144.google.com ([2a00:1450:4864:20::144]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gj2lg-0001aJ-5i for pgsql-www@lists.postgresql.org; Mon, 14 Jan 2019 13:59:10 +0000 Received: by mail-lf1-x144.google.com with SMTP id e26so15655688lfc.2 for ; Mon, 14 Jan 2019 05:59:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sJ1msq9AY2BMTtAdkEsM/tH3dJPjlFDsrQ82nRVwtyY=; b=gUVSheMsuELXB+jfv6/C52SJVV/oY4bR8IauZLEWP8Fc1zd5lCylzjYZsQExu+Tx0O 4REEzegT+YFpTEEily2pVKAxvZpiLQcPxGHTx6oMxzuBUNqbgsdX8zFVrmULTYlZxz2O vjhmAACmWcbEk629NOTzDEcbU26QsSEqmZ//+hc+j+ESen1xU1Z8fK3PSrjs8gBDZt8S 0rzNp/1FKYefKbKofLTK0nVY5MhxuSHktZFK3/eRjOFS5xatL1f3z1UGbGTNRasyWZOf uKiWu34N6LWJtKBnYpF2QgG/Trhi593t7zNZOtrZEQAEhIrGO1UyASV3crVHe7BGHBEr Nr3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sJ1msq9AY2BMTtAdkEsM/tH3dJPjlFDsrQ82nRVwtyY=; b=tkRtwaM2ANAw/kcBUlyLKqcwAeEw7JvuFiOF/L8vfPfKRrqSHQwZYkzcsmaIZUIolM VBve7Y2sYuNeu7LI+1fsdwoxp9kyhSf/+IPvCFV11M4vOJEdn/ljfTQ3K5T4rv8Di4Pk 9VgQRngjixXhkamdwMnCJ88KMLYEumoGyg5CmjtdplnHct+s6R94bB0wwQZW9jdd1AYN fqIuWI3Ni+pm+tIQqPXZA6WqgEwx1VDo97HGl88BNt9Ke9FG1ujQ1lq+kBL/B5Hi3oOF UCZW/E2xBOhh5kCSiXgJfIqoiUNWsgtpQb0mVs3kXnH8Fa4xPxmajoYdCRsMctEzHuEM Y2fg== X-Gm-Message-State: AJcUukcxIc8cJjEKbaoT5tiZg1rIzoG6hAuh6X76NkIOBjLTi89oK4SV FunUDMdiV5DkJwvqua2/BTQF3DmPxfYfB6zTAZSMKQ== X-Google-Smtp-Source: ALg8bN6aV1RSTj2nzMt8ZJX+UB9fS7ksLJINUfodHPX1qHgdMwfsSYSCOdtxfQOu7F9BKKKS/vk3f9oLc4Zb6TNqyRA= X-Received: by 2002:a19:5e5d:: with SMTP id z29mr13233699lfi.105.1547474345179; Mon, 14 Jan 2019 05:59:05 -0800 (PST) MIME-Version: 1.0 References: <14618.1547414109@sss.pgh.pa.us> In-Reply-To: <14618.1547414109@sss.pgh.pa.us> From: Magnus Hagander Date: Mon, 14 Jan 2019 14:58:53 +0100 Message-ID: Subject: Re: Wrong info in a commitfest page To: Tom Lane Cc: PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000a4d67c057f6b72b4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000a4d67c057f6b72b4 Content-Type: text/plain; charset="UTF-8" On Sun, Jan 13, 2019 at 10:15 PM Tom Lane wrote: > I happened to notice that > > https://commitfest.postgresql.org/21/1962/ > > shows the "latest attachment" as being from 2018-08-06, whereas > if you look at the thread, the latest attachment is pretty clearly > Heikki's in <16028522-316c-ec71-c065-91a1e1e004a2@iki.fi> of > 2018-12-30. Why is that? > > (The cfbot seems to be properly identifying the last attachment, > FWIW.) > Um. It's showing the one from 12-30 now, right? (Just to be clear, you are talking about the one that's at the bottom of the Email section?) Normally I'd say maybe the refresh job didn't have time to run, but it's two weeks back. Surely it must've run since then. My guess it had somehow not caught the changes from 12-30 (being Heikkis mail with the patch and your response). Then when Heikki sent his mail *today*, it triggered a refresh of the thread. We did change the archives from python2 to python3 on Jan 4th. But the changes from 12/30 should have been picked up already by then. There were no changes to the archives *or* the commitfest app between Dec 26 and Jan 4... There were explicit problems in the commitfest sync just after the changeover on Jan 4, but those syncs were re-run. Bottom line is, after some investigation I still don't really know where it got that from, but it looks like it fixed itself. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000a4d67c057f6b72b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Jan 13, 2019 at 10:15 PM Tom Lane= <tgl@sss.pgh.pa.= us> wrote:
I happened to notice that

https://commitfest.postgresql.org/21/1962/

shows the "latest attachment" as being from 2018-08-06, whereas if you look at the thread, the latest attachment is pretty clearly
Heikki's in <16028522-316c-ec71-c065-91a1e1e004a2@iki.fi&g= t; of
2018-12-30.=C2=A0 Why is that?

(The cfbot seems to be properly identifying the last attachment,
FWIW.)

Um. It's showing the one fro= m 12-30 now, right? (Just to be clear, you are talking about the one that&#= 39;s at the bottom of the Email section?)

Normally= I'd say maybe the refresh job didn't have time to run, but it'= s two weeks back. Surely it must've run since then.

My guess it had somehow not caught the changes from 12-30 (being Heik= kis mail with the patch and your response). Then when Heikki sent his mail = *today*, it triggered a refresh of the thread.

We did change the archives from python2 to python3 on Jan 4th. But the c= hanges from 12/30 should have been picked up already by then.=C2=A0 There w= ere no changes to the archives *or* the commitfest app between Dec 26 and J= an 4... There were explicit problems in the commitfest sync just after the = changeover on Jan 4, but those syncs were re-run.

= Bottom line is, after some investigation I still don't really know wher= e it got that from, but it looks like it fixed itself.

= --
=C2=A0Magnus Hagander
=C2=A0Me: = https://www.hagander= .net/
=C2=A0Work: https://www.redpill-linpro.com/
--000000000000a4d67c057f6b72b4--