[ Note that this is my first post on this list, and I'm posting via
gmane, so if I'm messing something up, please let me know, either
on-list, or in private, whichever you deem more appropriate ]
Danny Milosavljevic writes:
> Hi,
>
> Rust uses #![...] for something that is definitely not a
On Wed, Jan 22, 2020 at 01:23:26PM +0100, zimoun wrote:
> > > --8<---cut here---start->8---
> > > (define (make-you-get VIDEO-PLAYER PYTHON-VERSION WITH-FFMPEG)
> > > (package
> > > (inherit you-get
> > > #:add-inputs
> > > `(("PLAYER" ,VI
Hi guix,
After working on a few rust packages, it looks like there could be another step
on the process. There are a number of libraries in the crates registry that
wrap and vendor c libraries - libgit2, openssl, or jemalloc for example. The
wrapping libraries, for reference, are usually calle
The internal rowid's are used for builds as you can request builds by using
the rowid in the URL.
The motivation here is to enable running VACUUM operations in SQLite, without
risking the rowid's for Builds changing. It would be bad if they change, as
they're used in the URL's for builds.
* src/s
As it is unused from where db-add-input is called.
* src/cuirass/database.scm (db-add-input): Don't call and
return (last-insert-rowid).
---
src/cuirass/database.scm | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/src/cuirass/database.scm b/src/cuirass/database.scm
index 308
This will allow running multiple threads, that all listen on the same channel,
enabling processing multiple jobs at one time.
* src/cuirass/utils.scm (make-worker-thread-channel): Add a #:parallelism
argument, and create as many threads as the given parallelism.
---
src/cuirass/utils.scm | 24 +++
While this is a generic method, and initializer function will give the
flexibility required to create multiple worker threads for performing SQLite
queries, each with it's own database connection (as a result of calling the
initializer once for each thread). Without this change, they'd all have to
As far as I'm aware, it's necessary to use a separate thread for interacting
with SQLite as one of the threads used for fibers will be blocked while the
SQLite query is running.
This doesn't mean all queries have to be executed one at a time though,
providing the queries are executed outside the t
The number of threads is copied from bin/cuirass.in. When you have at least
two processors, this will allow database queries to be executed in parallel.
With some crude testing using the Apache HTTP server benchmarking tool (ab
from the httpd package), the max request latency does seem to drop whe
Hi Ludo,
On Thu, 23 Jan 2020 at 17:28, Ludovic Courtès wrote:
> I think we really need someone to pay attention to the schedule. It’s
> too hard for me and I guess for many of us to, at the same time, hack on
> new things, and sit down to prepare a release, which is often somewhat
> exciting.
As someone who just got a Pinebook Pro and is trying to use Guix on it, having
more frequent minor releases sounds really nice, if only because it’s a
longer-lived target and (I assume) would be more likely to have substitutes
available than current master. Building things on ARM takes a long ti
Hi!
Ricardo Wurmus skribis:
> Ludovic Courtès writes:
>
>> Regardless, I would go ahead and move (guix self) to Guile 3 now.
>
> Sounds good to me!
Done in 039cb8e6b11928639915eba40a9ead1bed1fef5f.
There’s a build failure on aarch64 that I’m tracking down:
http://ci.guix.info/build/2184296
Hi Gábor,
Gábor Boskovits skribis:
> This is a bit off topic, but I am about to create an automatic
> installer, that is
> a candidate for a new backend. It currently works by providing a configuration
> record, and then executes a few things from the installer.
>
> (It does a lookup for a candi
13 matches
Mail list logo
