From: | Akshat Jaimini <destrex271(at)gmail(dot)com> |
---|---|
To: | pgsql-www(at)lists(dot)postgresql(dot)org |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: [INFO] Regarding bugs in Testing Harness |
Date: | 2024-01-02 17:06:47 |
Message-ID: | CAMaW3ViEK3=hkR9bEeaHoNFfos5s_xnNMqdXZUGVqL_k39xL8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
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 PM Akshat Jaimini <destrex271(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2024-01-02 17:39:14 | Re: [INFO] Regarding bugs in Testing Harness |
Previous Message | Karl O. Pinc | 2024-01-02 15:07:34 | Re: Describing Postgres as "object-relational" on the home page |