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 1gj3mQ-0001iU-V9 for pgsql-www@arkaria.postgresql.org; Mon, 14 Jan 2019 15:03:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gj3mP-0000lk-Mb for pgsql-www@arkaria.postgresql.org; Mon, 14 Jan 2019 15:03:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gj3mP-0000ld-HA for pgsql-www@lists.postgresql.org; Mon, 14 Jan 2019 15:03:57 +0000 Received: from mail-lj1-x243.google.com ([2a00:1450:4864:20::243]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gj3mI-0006fG-Ec for pgsql-www@lists.postgresql.org; Mon, 14 Jan 2019 15:03:57 +0000 Received: by mail-lj1-x243.google.com with SMTP id t18-v6so19314459ljd.4 for ; Mon, 14 Jan 2019 07:03:50 -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=p4AUZFDyXFn7+avDxZxVG+fFE92L9pv1xhhNUBrYpaU=; b=SXevwybcqL4hJ/y8Lbr6eUK82bS1MdgvYjySxIz0ggSjri2kTt+XJ0jD61lxSAnV5z kiCIlHBrjvbkktbjiz5wsQZ+6Kod3vGkbwklkfkrhIeIKMAbc2QaqX/byRFwJ3gc02ZV 46xY5tKaNzpWQ8QSQ/jATFQEW+Li5PY/E1VW2qaEGCVHGCNvFyGEjPMn50WamcmZwhCh oQoDQw2jBq/pHgG5wumWdaFIQ58ogRJ5MrBKY3afk7l8gmsLgTf25iGObqWC10haSSoQ yQ/osfJRDRhYOikg8ABEHhVUfmdoTvRJkQUCcA1uAw7E/naHSp6ar/MMZI1yW/uT7KOy x5cg== 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=p4AUZFDyXFn7+avDxZxVG+fFE92L9pv1xhhNUBrYpaU=; b=rYodGiIdto9/Jwz9gO5Tyda1jK6P8Tb32/yVZTmq3sFZ+4wrcMlNBZEytaSkjJJ2HC RNWA0luIgPWk/N6/JtwrBVStVTWJdQo3y7PmG4hFSuaaXP/8lw+t4QtdHPsdbe3Scovq hKr+spygkxVdLGdATx7dAoSsNsInQguqyBko9PmUBDkC8MjhTm0K9D4Byhxos0UHARMQ nsZlDuXvdq6CcBtT9HhD68iLUn4HdpxLJmT3nf7J5U6ep3DoZ62whdKFrYw2GRiwgxRO HIKukV8xDNYtW/APLteWyM/oVDyVD4xNCsplyOWisNOlBZ12AWtoGSsRaSphfXfgP4+X i9QA== X-Gm-Message-State: AJcUukecjzaSv6IgOHLuImTH1MJrSTOzmLVF7Jd1OuapWPlsIZrMl5/L FGNKCNOLX50GCVXSP/5Fy+isTX2i/ZNmEkEUqztaXQ== X-Google-Smtp-Source: ALg8bN6B2ePy9xnkYLKFBfyTH/zJZV27qWpmN/s24xOpvsJ9iTA4ncRhf+Nom70qfy+w4hNwUpRYw+NCoO5mG0phAOk= X-Received: by 2002:a2e:3509:: with SMTP id z9-v6mr14278162ljz.54.1547478229491; Mon, 14 Jan 2019 07:03:49 -0800 (PST) MIME-Version: 1.0 References: <14618.1547414109@sss.pgh.pa.us> <23116.1547478111@sss.pgh.pa.us> In-Reply-To: <23116.1547478111@sss.pgh.pa.us> From: Magnus Hagander Date: Mon, 14 Jan 2019 16:03:38 +0100 Message-ID: Subject: Re: Wrong info in a commitfest page To: Tom Lane Cc: PostgreSQL WWW Content-Type: multipart/alternative; boundary="0000000000002abea1057f6c5a2e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000002abea1057f6c5a2e Content-Type: text/plain; charset="UTF-8" On Mon, Jan 14, 2019 at 4:01 PM Tom Lane wrote: > Magnus Hagander writes: > > 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? > > > 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?) > > Now it is, but it wasn't last night (and I did reload the page a few > times to eliminate client-side browser cache issues ...) > Yeah, that's what I figured. I believe it's the email from Heikki that triggered the refresh of the thread, but I have no idea why it was out of sync in the first place :( -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --0000000000002abea1057f6c5a2e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jan 14, 2019 at 4:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writ= es:
> 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> of
>> 2018-12-30.=C2=A0 Why is that?

> 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?)<= br>
Now it is, but it wasn't last night (and I did reload the page a few times to eliminate client-side browser cache issues ...)

Yeah, that's what I figured. I believe it's the e= mail from=C2=A0 Heikki that triggered the refresh of the thread, but I have= no idea why it was out of sync in the first place :(
=C2=A0
--
<= div>=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpr= o.com/
--0000000000002abea1057f6c5a2e--