From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 59493-done@debbugs.gnu.org
Subject: bug#59493: cuirass-remote-worker crash
Date: Sat, 26 Nov 2022 16:04:20 +0100 [thread overview]
Message-ID: <87edtp92q3.fsf@gnu.org> (raw)
In-Reply-To: <87k03lwtd7.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 23 Nov 2022 17:03:32 +0100")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
>> To me, ideally this would be either multi-threaded or Fiberized. The
>> latter would be more fruitful but what might be difficult is
>> guile-simple-zmq integration with Fibers (but maybe not: zmq_getsockopt
>> + ZMQ_FD lets us get the file descriptor of a socket).
>
> I would prefer the multi-threaded approach if possible. While the
> concept of Fiber is nice it adds another layer of complexity and
> instability to those programs which are already hard to debug.
I guess it’s not black and white. Shared-state multithreading is an
endless source of bugs, regardless of the language being used;
message-passing (what Fibers is about) is more tractable.
Sure Fibers can have bugs of its own (I’m well aware of that :-)) but at
Fiber-using code can be simpler and less error-ridden than the
equivalent shared-state code.
Anyway, we’re not there yet.
Can you remember the rationale for forking in remote-worker.scm, or do
you think we might as well do it all in a single process?
Thanks,
Ludo’.
prev parent reply other threads:[~2022-11-26 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 22:14 bug#59493: cuirass-remote-worker crash Ludovic Courtès
2022-11-23 8:08 ` Mathieu Othacehe
2022-11-23 15:47 ` Ludovic Courtès
2022-11-23 16:03 ` Mathieu Othacehe
2022-11-26 15:04 ` Ludovic Courtès [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=87edtp92q3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59493-done@debbugs.gnu.org \
--cc=othacehe@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).