MIME-Version: 1.0
References: 
 <CAMaW3VhRaUvSi_mR+_th7b=LQ3NZ-=Kg_aqTmAQpRXhC9zoDJg@mail.gmail.com>
 <CABUevEyiDjSY3iR6V-3EWqRmpgX490uVoxKWzCFXJUD5NOUvKQ@mail.gmail.com>
In-Reply-To: 
 <CABUevEyiDjSY3iR6V-3EWqRmpgX490uVoxKWzCFXJUD5NOUvKQ@mail.gmail.com>
From: Akshat Jaimini <destrex271@gmail.com>
Date: Wed, 4 Oct 2023 01:00:38 +0530
Message-ID: 
 <CAMaW3VgFmQH6Qz_5rE3mmGrSqNXk-0T0z_czufZOnMai2Yo61w@mail.gmail.com>
Subject: Re: Permission to allow testing harness to send error reports for
 pgweb directly to mailing list.
To: Magnus Hagander <magnus@hagander.net>, pgsql-www@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a42a530606d4ed28"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMaW3VgFmQH6Qz_5rE3mmGrSqNXk-0T0z_czufZOnMai2Yo61w%40mail.gmail.com>
Precedence: bulk

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

Hello,

> That is, if it finds the same issue on a later run, it must not re-send
the same thing. How does it work in regards to that today?

As per the current flow whenever a new commit is pushed to the pgweb repo,
the tests are executed. If some tests fail, an error report is sent with
the information of all the failed tests. So if that particular issue has
been resolved, the same report won't be sent but if some other commit is
pushed without resolving that particular issue then that particular error
will be reported again.

As far as the previous test runs have been considered, most of the errors
that have been caught are related to broken urls or some other small
problems that are usually fixed with a single commit so I don't think that
a single report would be re-sent that often.

If this functionality is required then I'll be more than happy to add it.
We can add some sort of a log/cache type structure that checks if a given
report with similar content has been sent to the mailing list in a given
time interval, let's say 15 days for now.

Regards,
Akshat Jaimini

On Wed, Oct 4, 2023 at 12:08=E2=80=AFAM Magnus Hagander <magnus@hagander.ne=
t> wrote:

> On Tue, Oct 3, 2023 at 8:24=E2=80=AFAM Akshat Jaimini <destrex271@gmail.c=
om>
> wrote:
> >
> > Hello everyone,
> > The testing harness has been successfull at catching multiple issues in
> pgweb in the past few months. The reports are for now being sent to me vi=
a
> email in case of any failure.
> >
> > Is it ok if  I can setup the harness to send the error reports directly
> to the mailing list?
>
>
> Hi!
>
> I think that would be reasonable, *if* it is ensured that a report is
> only sent once. That is, if it finds the same issue on a later run, it
> must not re-send the same thing. How does it work in regards to that
> today?
>
> --
>  Magnus Hagander
>  Me: https://www.hagander.net/
>  Work: https://www.redpill-linpro.com/
>

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

<div dir=3D"ltr"><div>Hello,</div><div><br></div><div>&gt; That is, if it f=
inds the same issue on a later run, it must not re-send the same thing. How=
 does it work in regards to that today?<br></div><div><br></div><div>As per=
 the current flow whenever a new commit is pushed to the pgweb repo, the te=
sts are executed. If some tests fail, an error report is sent with the info=
rmation of all the failed tests. So if that particular issue has been resol=
ved, the same report won&#39;t be sent but if some other commit is pushed w=
ithout resolving that particular issue then that particular error will be r=
eported again. <br></div><div><br></div><div>As far as the previous test ru=
ns have been considered, most of the errors that have been caught are relat=
ed to broken urls or some other small problems that are usually fixed with =
a single commit so I don&#39;t think that a single report would be re-sent =
that often. <br></div><div><br></div><div>If this functionality is required=
 then I&#39;ll be more than happy to add it. We can add some sort of a log/=
cache type structure that checks if a given report with similar content has=
 been sent to the mailing list in a given time interval, let&#39;s say 15 d=
ays for now.</div><div><br></div><div>Regards,</div><div>Akshat Jaimini<br>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Wed, Oct 4, 2023 at 12:08=E2=80=AFAM Magnus Hagander &lt;<a href=
=3D"mailto:magnus@hagander.net">magnus@hagander.net</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Oct 3, 2023 at 8=
:24=E2=80=AFAM Akshat Jaimini &lt;<a href=3D"mailto:destrex271@gmail.com" t=
arget=3D"_blank">destrex271@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello everyone,<br>
&gt; The testing harness has been successfull at catching multiple issues i=
n pgweb in the past few months. The reports are for now being sent to me vi=
a email in case of any failure.<br>
&gt;<br>
&gt; Is it ok if=C2=A0 I can setup the harness to send the error reports di=
rectly to the mailing list?<br>
<br>
<br>
Hi!<br>
<br>
I think that would be reasonable, *if* it is ensured that a report is<br>
only sent once. That is, if it finds the same issue on a later run, it<br>
must not re-send the same thing. How does it work in regards to that<br>
today?<br>
<br>
-- <br>
=C2=A0Magnus Hagander<br>
=C2=A0Me: <a href=3D"https://www.hagander.net/" rel=3D"noreferrer" target=
=3D"_blank">https://www.hagander.net/</a><br>
=C2=A0Work: <a href=3D"https://www.redpill-linpro.com/" rel=3D"noreferrer" =
target=3D"_blank">https://www.redpill-linpro.com/</a><br>
</blockquote></div>

--000000000000a42a530606d4ed28--