| Commit message (Collapse) | Author | Age |
|
|
|
| |
And change the default, as eq? doesn't always work.
|
| |
|
| |
|
|
|
|
| |
As this was causing problems with builtin:git-download.
|
|
|
|
| |
To help with debugging.
|
|
|
|
| |
As that makes debugging problems harder.
|
|
|
|
|
| |
As this will be useful for QA to say whether the package builds reproducibly
or not.
|
|
|
|
|
|
|
|
| |
Just have one fiber at the moment, but this will enable using fibers for
parallelism in the future.
Fibers seemed to cause problems with the logging setup, which was a bit odd in
the first place. So move logging to the parent process which is better anyway.
|
|
|
|
|
|
|
|
|
|
|
| |
This is mostly a workaround for the occasional problems with the guix-commits
mailing list, as it can break and then the data service doesn't learn about
new revisions until the problem is fixed.
I think it's still a generally good feature though, and allows deploying the
data service without it consuming emails to learn about new revisions, and is
a step towards integrating some kind of way of notifying the data service to
poll.
|
| |
|
|
|
|
| |
To handle characters like +.
|
|
|
|
|
| |
I'm not sure why this wasn't the way it worked previously. This should avoid
unconstrained use of PostgreSQL connections.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Better to timeout early.
|
|
|
|
| |
As one thread per core is probably unnecessary.
|
| |
|
|
|
|
|
|
| |
Now that squee cooperates with suspendable ports, this is unnecessary. Use a
connection pool to still support running queries in parallel using multiple
connections.
|
|
|
|
| |
In the compare package derivations response.
|
|
|
|
| |
This will keep the substitute information more up to date.
|
|
|
|
| |
So that triggering a check for substitutes can be integrated in.
|
| |
|
|
|
|
|
|
| |
So that this can be used by the qa-frontpage.
This should be improved and generalised.
|
|
|
|
| |
As this will help identify when the service restarts.
|
|
|
|
|
|
|
|
| |
In to two thread pools, a default one, and one reserved for essential
functionality.
There are some pages that use slow queries, so this should help stop those
pages block other operations.
|
|
|
|
|
|
|
|
|
|
| |
Harmonize "Build change" options between the selection menu and the
documentation
* guix-data-service/web/compare/html.scm (compare/package-derivations):
Replace "Still broken" with "Still failing" in the "Build change" help text.
Signed-off-by: Christopher Baines <mail@cbaines.net>
|
|
|
|
|
| |
As it's frequently useful to know how many packages/builds some change has
affected.
|
|
|
|
|
|
|
| |
The newer Guile Fibers web server will use the chunked transfer encoding when
a procedure is used and the content length is unspecified. This is good for
large responses, but unnecessary here. Also, there's a bug with the charset so
these changes to respond with correctly encoded bytevectors to avoid that.
|
|
|
|
|
|
|
|
|
| |
Newer versions of Guile Fibers will now use chunked encoding when a procedure
is used (and no content length is set). This is good, but not always what is
wanted, and there's also an issue with the port encoding.
This commit switches to responding with a string/bytevector when more
appropriate, plus explicitly setting the port encoding where that's needed.
|
| |
|
|
|
|
|
| |
This will allow for instrumenting low level database functionality, before
anything starts using the database.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In the /compare response.
This should enable qa.guix.gnu.org to detect when the base revision for a
comparison is unknown.
|
|
|
|
| |
As this is unused.
|
|
|
|
| |
As scheduling a build might unblock others.
|
|
|
|
| |
So that the queries don't get cancelled by the statement timeout.
|
| |
|
|
|
|
|
|
|
|
|
| |
This will hopefully provide a less expensive way of finding out if a scheduled
build is probably blocked by other builds failing or being canceled.
By working this out when the build events are recieved, it should be more
feasible to include information about whether builds are likely blocked or not
in various places (e.g. revision comparisons).
|
| |
|
|
|
|
|
| |
As the guix-data-service process seems to be using excessive amounts of
memory, and this will be useful to track it.
|
| |
|
| |
|
| |
|
|
|
|
| |
As this is a little clearer.
|
| |
|