Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qt8fk-00Azij-TO for pgsql-www@arkaria.postgresql.org; Wed, 18 Oct 2023 15:41:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qt8fi-005U2n-2K for pgsql-www@arkaria.postgresql.org; Wed, 18 Oct 2023 15:41:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qt8fh-005U25-RO for pgsql-www@lists.postgresql.org; Wed, 18 Oct 2023 15:41:22 +0000 Received: from mail-lf1-x143.google.com ([2a00:1450:4864:20::143]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qt8fg-0016rx-1L for pgsql-www@lists.postgresql.org; Wed, 18 Oct 2023 15:41:21 +0000 Received: by mail-lf1-x143.google.com with SMTP id 2adb3069b0e04-504a7f9204eso9284103e87.3 for ; Wed, 18 Oct 2023 08:41:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697643678; x=1698248478; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FmSksxk9enXbp9RcIjLT6EFQYTXvmshLLZE+0wkt5xU=; b=EFiQ8yzkSHKomTmPzsuaVW7PxtYBiUCMTtsASv++ZwBeqRtF8YnNES2RxpAjM8/dAx QjFWYk+MFke723dz5b6aXKyDBc2fkaykfrLypuN8NH2qA1Hdmz8q8OyFQTB3Iz7y6OSt iUmS4+voyJUYCwDNEdOWSmLcJrgosBDGGxsFlfZBSrDt++UJgyANxao8RcdYJTAIJmRM 4iGNa2Jxr6G+rYWpd6ZPrtK5T/6L+605vcTGrnp4cMmdE8BNCBrIy+GXcmNbkRQYKbV2 9hMyhpwOTZErpdJdtEsRx8MoYj+HZMC3I3A6kKUOvos/tNO4+b6pURbZJHfoRuiI3SDU qE9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697643678; x=1698248478; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FmSksxk9enXbp9RcIjLT6EFQYTXvmshLLZE+0wkt5xU=; b=C1pr77QAg2sIhK29il4l3eVzSi9Pl2aOnt5pH13PbUuQpQErZxoyl+0MsKLGEaMb/9 /w8C9aead0uQ+JnP52ZzBMB7riuwor3VEycQ3PsaQp8sfYuwYAVmuXaDHmtPDngRYNiS k3wDgrbY1la+VMjmKqNM1bYU4h4E49mwqDdIpbx2GurND6bfhQqREZkqJNQpEN1PIdnR 1/Hy0FR5Z0FYBA8aKnnJ/EARd9qdDTOJzHYdCm5TVyjt5koeqGVXPZsW6VJUddYaIQ3/ im5JFGy42CN79RjPybTIOF737g1MOrZuDTHCarAt34/yyRWyhPPD82CwdxCaUZwzMIJr NoqQ== X-Gm-Message-State: AOJu0YwWD+W+KTApPvb4QpF2xtTYLqACnB0RiFFHF8LBLgFujLIWA1fo f2P7kl0nC+oyYTDiD8v/U888Q+kgCzYJ+OME3rlrXzaUDSxW+Q== X-Google-Smtp-Source: AGHT+IEKu60ucExL6+xRHJy+GukVIrRJizjmwtd6fsXND8aTl413jAk2iE97yRrpOUGjnux4N+G5rHxCT+eIxXEGykA= X-Received: by 2002:ac2:53bc:0:b0:504:7e90:e05b with SMTP id j28-20020ac253bc000000b005047e90e05bmr4167377lfh.14.1697643678008; Wed, 18 Oct 2023 08:41:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Akshat Jaimini Date: Wed, 18 Oct 2023 21:11:06 +0530 Message-ID: Subject: Re: Possible Bug in events page To: Magnus Hagander Cc: pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000062096b0607ff78c2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000062096b0607ff78c2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Checked out the testing harness codebase. There was some issue with the timestamp generated for the events fixture as it was set to some previous date. Apologies for the false alarm. Regards, Akshat Jaimini On Wed, 18 Oct, 2023, 18:39 Magnus Hagander, wrote: > On Mon, Oct 16, 2023 at 6:01=E2=80=AFPM Akshat Jaimini > wrote: > > > > Hello everyone, > > Another possible bug was reported by the testing harness. There is a > particular test which adds and approves events and checks the events page > if the approved event is being displayed on it. > > This test was passing in the previous builds but a failure in displayin= g > the approved event was reported today. I was able to reproduce the issue = on > my local setup but wasn't able to find any changes that might have > triggered this. > > > > It would be great if someone could try to reproduce this issue to > confirm its validity. > > Hi! > > Nothing has changed in the events code for a long time. In fact, there > have been no code changes to pgweb in all of September and October, > only content changes. So if it passed a test before, but doesn't pass > it now, then something must've changed in the tests. > > -- > Magnus Hagander > Me: https://www.hagander.net/ > Work: https://www.redpill-linpro.com/ > --00000000000062096b0607ff78c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Checked out the testing harness codebase. There was s= ome issue with the timestamp generated for the events fixture as it was set= to some previous date.
Apologies for the false alarm.
=
Regards,
Akshat Jaimini

On Wed, 18 Oct, 2023, 18:39 Magnus Hagander, <magnus@hagander.net> wrote:
On Mon, Oct 16, 20= 23 at 6:01=E2=80=AFPM Akshat Jaimini <destrex271@gmail.com> wro= te:
>
> Hello everyone,
> Another possible bug was reported by the testing harness. There is a p= articular test which adds and approves events and checks the events page if= the approved event is being displayed on it.
> This test was passing in the previous builds but a failure in displayi= ng the approved event was reported today. I was able to reproduce the issue= on my local setup but wasn't able to find any changes that might have = triggered this.
>
> It would be great if someone could try to reproduce this issue to conf= irm its validity.

Hi!

Nothing has changed in the events code for a long time. In fact, there
have been no code changes to pgweb in all of September and October,
only content changes. So if it passed a test before, but doesn't pass it now, then something must've changed in the tests.

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