Re: [INFO] Regarding bugs in Testing Harness

Great! The harness is working properly now too.
Thanks!
I'll add another test to check the migration process too so that these
problems are also notified automatically.

Regards,
Akshat Jaimini

On Tue, Jan 2, 2024 at 11:09 PM Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> The whole table account_communityauthlastlogin is managed outside of
> the django ORM, because django doesn't support proper primary keys
> (see commit 9e70a4e0c32f8db0178f05dac4c1fca7b317e7c5).
>
> We don't have anything beyond this on the prod server, but it does
> look like this is just a plain bug in the commit, which breaks it. And
> the testing harness found it!
>
> Fix pushed in fbfe3cfc.
>
> //Magnus
>
>
> On Tue, Jan 2, 2024 at 6:07 PM Akshat Jaimini <destrex271(at)gmail(dot)com>
> wrote:
> >
> > 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
>