General

Profile

lucas (Lucas Nussbaum)

  • Login: lucas
  • Email: [email protected]
  • Registered on: 02/03/2009
  • Last sign in: 02/06/2015

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 16 16

Activity

10/13/2014

05:35 PM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
I was not interested in adding IPv6 support to my application, only in binding a port with a fallback mechanism. I worked around the problem with bind('0.0.0.0', 10001).
But I still think that it is wrong that TCPServer.new implements...
lucas (Lucas Nussbaum)
04:50 PM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
Indeed, bindv6only=1 seems to change this. However, bindv6only=1 is kind-of the default on all systems (except some Linux distros).
My goal was to implement the following:
try to bind port 10001 ; if already taken, bind port 10002
T...
lucas (Lucas Nussbaum)
11:41 AM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
correct copy/paste:
$ ./ruby -vrsocket -e 'p TCPServer::new(10001); system("netstat -ln|grep 10001"); p TCPServer::new(10001); system("netstat -ln|grep 10001"); p TCPServer::new(10001)'
ruby 2.2.0dev (2014-10-13 trunk 47902)...
lucas (Lucas Nussbaum)
11:37 AM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
I built Ruby 2.2 from source, and still encountered the same problem as the original report, with the exception that the bogus error message seems fixed:
$ ./ruby -vrsocket -e 'p TCPServer::new(10001); system("netstat -ln|grep 10001");...
lucas (Lucas Nussbaum)
07:10 AM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
It might be fixed in Ruby 2.2... I don't have an easy way to test. Akira, do you have an easy way to test with Ruby 2.1?
If it is indeed fixed, it might be worth backporting to 2.1.
lucas (Lucas Nussbaum)

09/05/2014

09:12 AM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
Also, a colleague using Arch Linux checked (using the same Ruby version). He doesn't have IPv6 enabled.
And he also got the "TypeError: no implicit conversion of nil into String" exception instead of the Errno::EADDRINUSE one.
lucas (Lucas Nussbaum)
07:25 AM Ruby Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
that was from the Debian package indeed. I haven't rebuilt Ruby from source. The Debian package does not carry any Debian-specific patch at the moment. You cannot reproduce it? lucas (Lucas Nussbaum)

09/04/2014

03:20 PM Ruby Bug #10203 (Closed): TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
after:
irb(main):003:0> TCPServer::new(10001)
=> #<TCPServer:fd 9>
I get irb listening to port 10001 using IPv4, but not IPv6:
tcp 0 0 0.0.0.0:10001 0.0.0.0:* LISTEN 1000 376068 24437/irb
a se...
lucas (Lucas Nussbaum)

11/12/2011

03:10 AM Ruby Bug #5244: Continuation causes Bus Error on Debian sparc
Dear Ruby developers,
Could you follow up on this issue?
The fix that was commited is not correct, as explained in comment #19. A correct fix is in comment #20.
Also, could you backport this to the ruby1_9_3 branch?
lucas (Lucas Nussbaum)

10/26/2011

01:23 AM Ruby Feature #5481: Gemifying Ruby standard library
On 25/10/11 at 22:43 +0900, Yusuke Endoh wrote:
> Hello,
>
> 2011/10/25 Lucas Nussbaum <[email protected]>:
> > Instead, I would prefer a plan where the interpreter no longer releases with the stdlib, but just releases w...
lucas (Lucas Nussbaum)

Also available in: Atom