From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Alexey Abramov <levenson@mmer.org>
Cc: guile-user@gnu.org
Subject: Re: 8sync error in procedure select
Date: Tue, 04 May 2021 14:58:12 -0400 [thread overview]
Message-ID: <8735v2wcl7.fsf@dustycloud.org> (raw)
In-Reply-To: <87zgxbn72d.fsf@delta.lan>
Hi! Hm... it might make sense to try switching to the "fibers" branch
of 8sync and see if that does better?
I guess I haven't worked on 8sync in some time, but really, the
intention was to switch it over to being on top of Fibers... Andy knew
more about building an event loop than I did ;P
Alexey Abramov writes:
> Hi,
>
> I am trying to test an actor I wrote with 8sync. I created a probe actor
> which sends messages to the main one. A problem I am having is that when
> I want to send a *cleanup* to the main (server) actor from the probe, I
> am getting the following backtrace:
>
> --8<---------------cut here---------------start------------->8---
> λ guile --debug -s tests/test.scm
> Backtrace:
> In ice-9/boot-9.scm:
> 1736:10 11 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
> 10 (apply-smob/0 #<thunk 7fac09a7b9a0>)
> In ice-9/boot-9.scm:
> 718:2 9 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
> In ice-9/eval.scm:
> 619:8 8 (_ #(#(#<directory (guile-user) 7fac096a0f00>)))
> In ice-9/boot-9.scm:
> 2806:4 7 (save-module-excursion _)
> 4351:12 6 (_)
> In 8sync/actors.scm:
> 812:6 5 (run-hive #<<hive> 7fac08bdd0c0> _ #:cleanup _ # _)
> In ice-9/control.scm:
> 91:24 4 (call-with-escape-continuation _)
> In 8sync/agenda.scm:
> 569:6 3 (run-agenda #<<agenda> queue: (() . #f) prompt-tag: ("…> …)
> 470:7 2 (update-agenda-from-select! #<<agenda> queue: (() . #f)…>)
> In ice-9/boot-9.scm:
> 1731:15 1 (with-exception-handler #<procedure 7fac08bbd240 at ic…> …)
> In unknown file:
> 0 (select (#<closed: file 7fac07ff6460>) () () #f #f)
>
> ERROR: In procedure select:
> In procedure select: Wrong type argument in position 1: #<closed: file 7fac07ff6460>
> --8<---------------cut here---------------end--------------->8---
>
> I have attached a simple snippet to reproduce the problem, and also a
> naive patch I did. I am not sure if it is me doing the shutdown wrong, or
> it's a bug.
prev parent reply other threads:[~2021-05-04 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 15:57 8sync error in procedure select Alexey Abramov
2021-05-04 18:58 ` Christopher Lemmer Webber [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735v2wcl7.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=levenson@mmer.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.
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).