New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rapid network interaction crashes something #6044
Comments
From robertle@semistable.comhi everyone, I have these two tiny pieces of code: ---------------------------8<-- server.p6 -------------------------- ---------------------------8<-- client.p6 -------------------------- --------------------------->8--------------------------------------- I start up the server and then the client, which runs for about 20s and if you remove the sleep in the client, the server process stops at some This is Rakudo version 2017.01-132-g97359ae built on MoarVM version please let me know if there is anything I can do to help debug or thanks robert -- |
From @zoffixznetOn Wed, 01 Feb 2017 09:03:37 -0800, robertle@semistable.com wrote:
Can't reproduce on 2017.01-121-gf94cb21. Your client script is using $conn_count and $echo_count but neither is defined. What values are those supposed to be at? Is there anything else missing? |
The RT System itself - Status changed from 'new' to 'open' |
From robertle@semistable.comapologies for a possible duplication, I thought replying to the email would On Thu, 02 Feb 2017 10:38:10 -0800, cpan@zoffix.com wrote:
sorry, didn't mean to snip these off. they are: my $conn_count = 10000; otherwise there is only a "use v6;" and a shebang in each file. I donm't I just retried it, with the "say" line it works, without the say the |
From robertle@semistable.comOn Thu, Feb 02, 2017 at 10:38:10AM -0800, Zoffix Znet via RT wrote:
sorry, didn't mean to snip these off. they are: my $conn_count = 10000; otherwise there is only a "use v6;" and a shebang in each file. I donm't I just retried it, with the "say" line it works, without the say the regards robert -- |
Migrated from rt.perl.org#130689 (status was 'open')
Searchable as RT130689$
The text was updated successfully, but these errors were encountered: