[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>
I would like to request developers meeting around April 17 or 18 in this month.
14 messages
2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014
— Urabe Shyouhei <shyouhei@...>
2014/04/03
It's good if we have a meeting then.
[#61826] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/03
Regarding openssl issues, I’ve discussed possible meeting time with Martin last month and he seemed positive.
[#61833] Re: Plan Developers Meeting Japan April 2014
— Martin Bo煬et <martin.bosslet@...>
2014/04/03
Hi,
[#61847] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/03
Martin Boテ殕et <martin.bosslet@gmail.com> wrote:
[#61849] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I will post summary of meeting on Google docs after the meeting.
[#61852] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/04
Zachary Scott <e@zzak.io> wrote:
[#61860] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I’m ok with redmine, thanks for bringing up your concern!
[#62076] Candidacy to 2.1 branch maintainer. — Tomoyuki Chikanaga <nagachika00@...>
Hello,
7 messages
2014/04/17
[#62078] Re: Candidacy to 2.1 branch maintainer.
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/04/17
> And does anyone have counter proposal for 2.1 maintenance?
[ruby-core:62073] [ruby-trunk - Bug #9753] [Open] UNIX Socket doesn't handle multiple clients
From:
thomas.lynch@...
Date:
2014-04-17 10:31:40 UTC
List:
ruby-core #62073
Issue #9753 has been reported by Thomas Lynch.
----------------------------------------
Bug #9753: UNIX Socket doesn't handle multiple clients
https://bugs.ruby-lang.org/issues/9753
* Author: Thomas Lynch
* Status: Open
* Priority: High
* Assignee:
* Category:
* Target version:
* ruby -v: ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
When a first client session is still active, a second client session starting then closing its connection causes the first session to hang.
This can be reproduced every time by using the included source files and these directions:
A. open three terminals, say T1,T2, and T3
1. in T1 start the server2
> ./simple_server2.rb
2. in T2 run the slow client and see that it works
> ./simple_client_slow.rb
3. in T3 run the regular client and see that it works too
> ./simple_client.rb
B. now go back to T2 and run simple_client_slow, then reasonably quickly
go to T3 and run simple_client
what you will see: simple_client finishes first, and simple_slow hangs
Note also the enclosed screen shots showing the hang.
Hanging sessions with no known workaround for Unixsockets is fairly serious so I'll set this to priority high. I didn't set it to urgent because the code can be rewritten to use TCP sockets, however it is unknown of the problem is there also.
---Files--------------------------------
simple_server2.rb (482 Bytes)
simple_client_slow.rb (578 Bytes)
simple_client.rb (407 Bytes)
Screenshot from 2014-04-17 09_50_35.png (74 KB)
Screenshot from 2014-04-17 09_53_26.png (82 KB)
--
https://bugs.ruby-lang.org/