public inbox for [email protected]  

help / color / mirror / Atom feed

From: Daniel Gustafsson <[email protected]>
To: Akshat Jaimini <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: [email protected]
Subject: Re: Permission to allow testing harness to send error reports for pgweb directly to mailing list.
Date: Thu, 5 Oct 2023 17:02:39 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMaW3VgFmQH6Qz_5rE3mmGrSqNXk-0T0z_czufZOnMai2Yo61w@mail.gmail.com>
References: <CAMaW3VhRaUvSi_mR+_th7b=LQ3NZ-=Kg_aqTmAQpRXhC9zoDJg@mail.gmail.com>
	<CABUevEyiDjSY3iR6V-3EWqRmpgX490uVoxKWzCFXJUD5NOUvKQ@mail.gmail.com>
	<CAMaW3VgFmQH6Qz_5rE3mmGrSqNXk-0T0z_czufZOnMai2Yo61w@mail.gmail.com>

> On 3 Oct 2023, at 21:30, Akshat Jaimini <[email protected]> wrote:

> > 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. 

That doesn't seem terribly great, while bugs and errors should be fixed when
found, sending reports of them repeatedly risk reporting-fatigue.  Publishing
this report to a website would handle that I think.

One question, would this test harness detect and report potential security
issues like XSS?  If so we should probably limit the audience of the report..


--
Daniel Gustafsson

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Permission to allow testing harness to send error reports for pgweb directly to mailing list.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox