MIME-Version: 1.0
References: 
 <CAMaW3VgbJmp8BQw_QUshk4JfFhOco--ymhEwjwGRTvftzqpiZg@mail.gmail.com>
In-Reply-To: 
 <CAMaW3VgbJmp8BQw_QUshk4JfFhOco--ymhEwjwGRTvftzqpiZg@mail.gmail.com>
From: Akshat Jaimini <destrex271@gmail.com>
Date: Tue, 2 Jan 2024 22:36:47 +0530
Message-ID: 
 <CAMaW3ViEK3=hkR9bEeaHoNFfos5s_xnNMqdXZUGVqL_k39xL8Q@mail.gmail.com>
Subject: Re: [INFO] Regarding bugs in Testing Harness
To: pgsql-www@lists.postgresql.org
Cc: Magnus Hagander <magnus@hagander.net>
Content-Type: multipart/alternative; boundary="000000000000c2af41060df986be"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMaW3ViEK3%3DhkR9bEeaHoNFfos5s_xnNMqdXZUGVqL_k39xL8Q%40mail.gmail.com>
Precedence: bulk

--000000000000c2af41060df986be
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Turns out the harness was not able to build the website locally in the dev
environment. This is due to the recent patch for 'making the foreign key
from last login table be ON DELETE CASCADE'. As far as I understood from
the commit message this needs to be handled by postgres instead of Django.
Have we implemented something on our production server which allows this?
If yes then kindly share that so we can get the harness back up and
running. Currently, it is unable to parse the file
'pgweb/account/migrations/0004_cauth_last_login.py' while running
migrations.

Regards,
Akshat Jaimini

On Tue, Jan 2, 2024 at 1:37=E2=80=AFPM Akshat Jaimini <destrex271@gmail.com=
> wrote:

> Hi,
> This is to update that recently the accessibility tests of the testing
> harness are not working as intended. Currently looking into the possible
> causes. This might take a few days to get back up and running; The
> functionality tests are running for now.
>
> Regards,
> Akshat Jaimini
>

--000000000000c2af41060df986be
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Turns out the harness was not able to bui=
ld the website locally in the dev environment. This is due to the recent pa=
tch for &#39;making the foreign key from last login table be ON DELETE CASC=
ADE&#39;. As far as I understood from the commit message this needs to be h=
andled by postgres instead of Django. Have we implemented something on our =
production server which allows this? If yes then kindly share that so we ca=
n get the harness back up and running. Currently, it is unable to parse the=
 file &#39;pgweb/account/migrations/0004_cauth_last_login.py&#39; while run=
ning migrations.</div><div dir=3D"ltr"><br></div><div>Regards,</div><div>Ak=
shat Jaimini<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Jan 2, 2024 at 1:37=E2=80=AFPM Akshat Jaimini &lt;<=
a href=3D"mailto:destrex271@gmail.com" target=3D"_blank">destrex271@gmail.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr"><div>Hi,</div><div>This is to update that recently the a=
ccessibility tests of the testing harness are not working as intended. Curr=
ently looking into the possible causes. This might take a few days to get b=
ack up and running; The functionality tests are running for now.<br></div><=
div><br></div><div>Regards,</div><div>Akshat Jaimini<br></div></div>
</blockquote></div></div>

--000000000000c2af41060df986be--