From: Linas Vepstas <linasvepstas@gmail.com>
To: Artyom Poptsov <poptsov.artyom@gmail.com>
Cc: Guile Users' Mailing List <guile-user@gnu.org>
Subject: Re: On the Guile-SSH future
Date: Sun, 2 Jun 2019 15:39:33 -0500 [thread overview]
Message-ID: <CAHrUA36kvwW3fXw6m+ZA4qfuni79MLJ_5saU+fOriJFPYdd8WQ@mail.gmail.com> (raw)
In-Reply-To: <87woiv1vkw.fsf@gmail.com>
FYI, I've written a guile telnet server; unfortunately it is deeply buried
in another project and would be hard to abstract.
Why do this? Well, because the default guile-2.2 network REPL server was
slow, would crash, deadlock, have terrible response times, etc. making it
embarrassingly unusable.
I spent an afternoon googling around for a generic telnet/ssh/ssl/whatever
interactive network login terminal server, and, amazingly, got nothing. One
might think that many people/projects/organizations might have a
stand-alone interactive shell of some kind, and needed to slap an
ssh/telnet/whatever interface on it. Why doesn't such a thing exist?
Maybe because it sounds easy, at first, until you hit the scalability &
reliability and throughput and latency issues, and then ... well, it gets
really hard and really painful to debug. Whatever. Yes, the world needs
one of these.
-- Linas
On Sun, May 12, 2019 at 11:33 AM Artyom Poptsov <poptsov.artyom@gmail.com>
wrote:
> Hello Guilers.
>
> For those of you who interested in a new release of Guile-SSH [1]:
>
> I *do not* lost an interest in the project, I'm just buried under my
> jobs and other tasks. Yet I'm trying to allocate some time slices for
> Guile-SSH. For example, I just merged the new implementation of RREPL
> (stateless RREPL, thanks to Ludovic for the idea) to the master branch.
>
> Currently one of the main showstoppers for the project is the
> implementation of the tests: they're failing sometimes and sometimes get
> stuck due to some kind of dead-lock or something. I'm tired of dragging
> the current implementation with all its "quirks" from release to
> release, so there's a burning need to fix it somehow or re-implement the
> testing for the project altogether. So I guess I'm not going to make a
> release untill the problem is fixed.
>
> Many problems with the tests are arising from the fact that Guile-SSH
> needs multi-process tests (i.e. client-server tests) and SRFI-64 alone
> that I use for tests seems to be a little bit insufficient on its own
> for such tests, so I built some kind of a testing framework upon it.
>
> I'd appreciate any testing and help.
>
> Thanks,
>
> - Artyom
>
> [1] https://github.com/artyom-poptsov/guile-ssh
>
> --
> Artyom V. Poptsov <poptsov.artyom@gmail.com>
> Home page: http://poptsov-artyom.narod.ru/
> CADR Hackerspace co-founder: https://cadrspace.ru/
> GPG: D0C2 EAC1 3310 822D 98DE B57C E9C5 A2D9 0898 A02F
>
--
cassette tapes - analog TV - film cameras - you
prev parent reply other threads:[~2019-06-02 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 16:33 On the Guile-SSH future Artyom Poptsov
2019-05-12 21:27 ` Arne Babenhauserheide
2019-05-15 21:56 ` Ludovic Courtès
2019-06-02 20:39 ` Linas Vepstas [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=CAHrUA36kvwW3fXw6m+ZA4qfuni79MLJ_5saU+fOriJFPYdd8WQ@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=guile-user@gnu.org \
--cc=poptsov.artyom@gmail.com \
/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).