unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: "guix deploy" is in git master
Date: Thu, 11 Jul 2019 12:58:09 -0400	[thread overview]
Message-ID: <878st4qzj2.fsf@sdf.lonestar.org> (raw)
In-Reply-To: <87pnmgtw4b.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 11 Jul 2019 17:43:32 +0200")

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hi, Chris + Ludovic!

Ludovic Courtès <ludo@gnu.org> writes:

> Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
>
>> You can spawn a bunch of threads, then use Guile's channels to
>> synchronize with the main thread.  (Not to be confused with Guix's
>> channels!)
>
> I think you mean Fibers channels, right?
>
> You could also try to simply use ‘par-map’ and the likes, but be
> cautious when you start dreading into that: you’ll have to make sure
> you don’t share SSH sessions or ports between threads, that you don’t
> modify shared vlists/vhashes, etc.
>
> Ludo’.

Thanks for the suggestions, I'll look into these. 'deploy-machine' is
reasonably self-contained, so the only issue that's coming to mind at
the moment is if someone were to explicitly share sessions through the
'session' field of 'machine-ssh-configuration'.

Regards,
Jakob

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2019-07-11 16:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06  6:17 "guix deploy" is in git master Christopher Lemmer Webber
2019-07-05 23:33 ` Jakob L. Kreuze
2019-07-05 23:34 ` Jakob L. Kreuze
2019-07-06  9:29 ` Ricardo Wurmus
2019-07-06 11:51   ` Jakob L. Kreuze
2019-07-06  9:23     ` Christopher Lemmer Webber
2019-07-06 17:22       ` Ricardo Wurmus
2019-07-06 17:17         ` Christopher Lemmer Webber
2019-07-07  0:12         ` Mark H Weaver
2019-07-07  7:55           ` Ricardo Wurmus
2019-07-07  6:55             ` Christopher Lemmer Webber
2019-07-08 17:15           ` Jakob L. Kreuze
2019-07-07  8:05   ` Ricardo Wurmus
2019-07-07 14:45     ` Ludovic Courtès
2019-07-08 17:37       ` Jakob L. Kreuze
2019-07-08 19:27         ` Ricardo Wurmus
2019-07-08 20:11           ` Jakob L. Kreuze
2019-07-08 20:16             ` Jakob L. Kreuze
2019-07-08 20:23               ` Ricardo Wurmus
2019-07-10 13:51           ` Thompson, David
2019-07-10 17:39             ` Jakob L. Kreuze
2019-07-11  4:27               ` Christopher Lemmer Webber
2019-07-11 15:43                 ` Ludovic Courtès
2019-07-11 16:58                   ` Jakob L. Kreuze [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878st4qzj2.fsf@sdf.lonestar.org \
    --to=zerodaysfordays@sdf.lonestar.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).