On 09/08/18 18:54, Daniel Axtens wrote:
This series starts work on the latter of these by addressing yet another
issues, #22 [3]. Full details of the feature are provided inline but
tl;dr labels are arbitrary bits of metadata that can be used to
represent some of the more orthogonal states like "
On Fri, 10 Aug 2018 01:08:48 +1000
Daniel Axtens wrote:
> Daniel Black writes:
>
> > An empty environment variable resulted in localhost, meaning
> > posgresql connecting to domain sockets wasn't available.
>
> It took me a long time to understand how this works (e.g. that PGPORT
> is still
On Fri, 10 Aug 2018 01:12:28 +1000
Daniel Axtens wrote:
> Hi Daniel,
>
> > +matrix:
> > + include:
> > +- addons:
> > +postgresql: "10"
> > +apt:
> > + packages:
> > + - postgresql-10
> > + - postgresql-client-10
> > + env:
> > +- PGPO
Hi Daniel,
> +matrix:
> + include:
> +- addons:
> +postgresql: "10"
> +apt:
> + packages:
> + - postgresql-10
> + - postgresql-client-10
> + env:
> +- PGPORT=5433
> +- PW_TEST_DB_PORT=5433
> +- PW_TEST_DB_TYPE=postgres
>
Daniel Black writes:
> An empty environment variable resulted in localhost, meaning
> posgresql connecting to domain sockets wasn't available.
It took me a long time to understand how this works (e.g. that PGPORT is
still required to be set for psql to find the correct domain socket.)
But I thin
On Thu, Aug 09, 2018 at 11:55:16AM +1000, Stewart Smith wrote:
Out of interest, does the kernel.org instance back onto PostgreSQL or
MySQL?
We have one of each. The original instance patchwork.kernel.org is on
MySQL (well, MariaDB), because that's the database cluster we have in
our PDX DC.
Stephen Finucane writes:
> I want to add support for global series states, as noted in #157 [1]
> However, to get there we're going to need a boolean open/closed
> attribute for 'Patch.state' and to get _there_ we're going to need to
> clean up the various 'State' fixtures, as noted in #4 [2].
I
In constructing the list of patches for a project, there are two
main queries that are executed:
1) get a count() of how many patches there are
2) Get the page of results being displayed
In a test dataset of ~11500 LKML patches and ~4000 others, the existing
code would take around 585ms and 858ms