Hello Ludo,
Ludovic Courtès writes:
> Thiago Jung Bauermann skribis:
>
>> I tried the latter a couple of weeks ago and it didn't work either,
>> though it's highly likely that I did something wrong in my Scheme code.
>> I also didn't use the 1-second timer hack so perhaps that was it.
>>
>>
Ludovic Courtès schreef op zo 15-05-2022 om 22:59 [+0200]:
> How does a basic SIGCHLD handler fare?
>
> (sigaction SIGCHLD
> (lambda _ (false-if-exception (waitpid WAIT_ANY WNOHANG
Will we get two SIGCHLD when two subprocesses exit at the same time, or
only a single one? If they are
Hello zimoun,
zimoun writes:
> Hi Thiago,
>
> On Fri, 06 May 2022 at 00:22, Thiago Jung Bauermann
> wrote:
>
>> I didn't go that route because I don't like disabling tests without
>> understanding why they fail and it took me a while to understand the
>> zombie root cause. In addition to
Hi,
Thiago Jung Bauermann skribis:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Maxim Cournoyer skribis:
>>
>>> Yes, that would be the correct and general solution (I hope you get to
>>> fix it, else I may look into it in some time). Workarounds currently in
>>> use can be seen in our mutter
Hi Kyle,
Thanks for the details and explanations.
On Sun, 08 May 2022 at 00:41, Kyle Meyer wrote:
> I'd eventually like to be able to follow list with lei via piem's
> interface, but things aren't there yet.
All in all, I would like that the public-inbox format would be indexed
by Notmuch
zimoun writes:
> [...]
> Well, using the plain Git repo, it is easy to:
>
> 1. get messages from a list starting at a date;
> using ’git clone --mirror --shallow-since=’
>
> 2. get all the new messages;
> (using ’git pull)
>[...]
> IIUC, ’lei’ avoid this manual dance with the Git repo
Hello,
Ludovic Courtès writes:
> Hi,
>
> Maxim Cournoyer skribis:
>
>> Yes, that would be the correct and general solution (I hope you get to
>> fix it, else I may look into it in some time). Workarounds currently in
>> use can be seen in our mutter package definition (it's a bit
Hi,
Maxim Cournoyer skribis:
> Yes, that would be the correct and general solution (I hope you get to
> fix it, else I may look into it in some time). Workarounds currently in
> use can be seen in our mutter package definition (it's a bit convoluted,
> having to fork a process in which we set
Hi Thiago,
On Fri, 06 May 2022 at 00:22, Thiago Jung Bauermann
wrote:
> I didn't go that route because I don't like disabling tests without
> understanding why they fail and it took me a while to understand the
> zombie root cause. In addition to that, without the testsuite passing I
> didn't
Hi Kyle,
Thanks for the answer.
On Thu, 05 May 2022 at 22:24, Kyle Meyer wrote:
> zimoun writes:
>> How do you query all new ones for a specific list?
>
> Rather than pass --all, you can call `lei up OUTPUT', where OUTPUT is a
> particular saved search generated by `lei q', so you could have
Hello,
zimoun writes:
> On Wed, 04 May 2022 at 21:49, Kyle Meyer wrote:
>
>> I've tried sit down and update Guix's public-inbox definition a few
>> times, but there are various test failures that I didn't figure out how
>> to handle in the time I had. (IIRC, I think they're related to the
Hello,
Maxim Cournoyer writes:
> Hi,
>
> Thiago Jung Bauermann writes:
>
> [...]
>
>>> (IIRC, I think they're related to the lei tests expecting to be able
>>> to kill the lei-daemon process, which isn't the case in Guix's build
>>> environment.)
>>
>> Yes, that's what I'm seeing as well.
zimoun writes:
> …why not just disable the specific test or if not possible, turn off the
> test suite ’#:tests? #f’. Whereas it is not the best, it would allow to
> have ’lei’ while waiting the fix at the Guix build environment level.
>
> WDYT?
public-inbox has a good test suite, so it'd be
Hi,
Thiago Jung Bauermann writes:
[...]
>> (IIRC, I think they're related to the lei tests expecting to be able
>> to kill the lei-daemon process, which isn't the case in Guix's build
>> environment.)
>
> Yes, that's what I'm seeing as well. The lei-daemon process is actually
> killed, but
Hi Kyle and Thiago,
Reading your both answers…
On Wed, 04 May 2022 at 21:49, Kyle Meyer wrote:
> I've tried sit down and update Guix's public-inbox definition a few
> times, but there are various test failures that I didn't figure out how
> to handle in the time I had. (IIRC, I think they're
Kyle Meyer writes:
> zimoun writes:
>
>> On Tue, 03 May 2022 at 17:42, Thiago Jung Bauermann
>> wrote:
> [...]
>>> Just an aside about public-inbox: Starting with version 0.7 it ships
>>> with a ‘lei’ tool that can be used to query a local or remote
>>> public-inbox repo, and export the
zimoun writes:
> On Tue, 03 May 2022 at 17:42, Thiago Jung Bauermann
> wrote:
[...]
>> Just an aside about public-inbox: Starting with version 0.7 it ships
>> with a ‘lei’ tool that can be used to query a local or remote
>> public-inbox repo, and export the matching messages to a maildir.
>
>
Hi,
On Tue, 03 May 2022 at 17:42, Thiago Jung Bauermann
wrote:
> zimoun writes:
>
>> Instead of subscription, public-inbox provides the archives as a Git
>> repo. Therefore, being up to date just becomes “guix pull” and the Git
>> repo can be transformed to Maildir using e.g.,
>>
>> $git
Hello zimoun,
zimoun writes:
> Instead of subscription, public-inbox provides the archives as a Git
> repo. Therefore, being up to date just becomes “guix pull” and the Git
> repo can be transformed to Maildir using e.g.,
>
> $git rev-list | while read sha; do
> $git show $sha:m >
Hi zimoun,
> Is the update of Mumi done?
Mumi has been patched with a proof-of-concept GraphQL API. See
https://git.elephly.net/gitweb.cgi?p=software/mumi.git;a=commit;h=f5232c49fe8a3b127c96f7b502775f16aebf3033
But, I don't know if mumi has been reconfigured on berlin yet. Still
waiting on
Hi Arun,
On Wed, 27 Apr 2022 at 16:44, Arun Isaac wrote:
> Yes, with the update, Mumi will have a GraphQL API. GraphQL APIs are
> more flexible than traditional REST APIs. See https://graphql.org/ for
> more.
Is the update of Mumi done?
Well, this GraphQL API could ease the current workflow,
Hi zimoun,
> The update of Mumi adds a GraphQL thing to issues.guix.gnu.org, IIUC.
Yes, with the update, Mumi will have a GraphQL API. GraphQL APIs are
more flexible than traditional REST APIs. See https://graphql.org/ for
more.
At some point, I plan to add support for identifying a message
Hi,
On Fri, 22 Apr 2022 at 11:08, Arun Isaac wrote:
> I would like to update the mumi running on berlin to the latest
> version.
The update of Mumi adds a GraphQL thing to issues.guix.gnu.org, IIUC.
Quoting Ricardo from #guix-hpc [1].
--8<---cut
Hi Maxim,
I would like to update the mumi running on berlin to the latest
version. I spoke to Ricardo off-list and he tells me that there are
issues running `guix system reconfigure' on the server. Are there any
updates on that?
Thanks,
Arun
24 matches
Mail list logo
