| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
I think the idle connections associated with idle threads are still taking up
memory, so especially now that you can configure an arbitrary number of
threads (and thus connections), I think it's good to close them regularly.
|
| |
|
|
| |
And double the default to 16.
|
| |
|
|
|
|
|
|
|
| |
The server part of the guix-data-service doesn't work great as a guix service,
since it often fails to start if the migrations take any time at all.
To address this, start the server before running the migrations, and serve the
pages that work without the database, plus a general 503 response. Once the
migrations have completed, switch to the normal behaviour.
|
| |
|
|
| |
This is a step towards having up to date substitute availability data.
|
| |
|
|
| |
Introduced in 0dc05982cde052c985bb440dc026cbe3334ee50b.
|
| |
|
|
|
| |
Since this rolls back migrations less, which is good when the rollback bit
isn't always implemented.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This was good in that it avoided having to deal with long running connections,
but it probably takes some time to open the connection, and these changes are
a step towards offloading the PostgreSQL queries to other threads, so they
don't block the threads for fibers.
|
| |
|
|
|
| |
This will help stop queries running for an unnecessarily long time, longer
than NGinx will wait for example.
|
| |
|
|
| |
Move it after the output relating to narinfo signing, and include the host.
|
| |
|
|
|
| |
Adjust the previously unused error page code, and start to use it. Only show
the error if configured to do so, to avoid leaking secret information.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Allow for build status information to be submitted by POST request. This
required some changes to the builds and build_status tables, as for example,
the Cuirass build id may not be available, and the derivation may not be know
yet, so just record the derivation file name.
|
| |
|
|
| |
As this means that like psql, the unix socket will be used.
|
| |
|
|
|
| |
As these are used for logging, which is done on a line by line basis. Remove
the now redundant calls to (force-output).
|
| | |
|
| |
|
|
|
| |
This'll help the a service manager (like the shepherd) know when the service
is ready, which at the moment, means the database migrations have happened.
|
| |
|
|
| |
As this means it can find the relevant files.
|
| |
|
|
| |
So that it can always find psql.
|
| | |
|
| |
|
|
|
|
| |
This runs Sqitch on startup, which should make managing the database easier,
as you just have to restart the service with this option, and the database
should be updated if necessary.
|
|
|
This is a service designed to provide information about Guix. At the
moment, this initial prototype gathers up information about packages,
the associated metadata and derivations.
The initial primary use case is to compare two different revisions of
Guix, detecting which packages are new, no longer present, updated or
otherwise different.
It's based on the Mumi project.
[1]: https://git.elephly.net/software/mumi.git
|