[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60561] [ruby-trunk - Bug #9477] [Closed] Address family not supported by protocol - socket(2) - udp
From:
akr@...
Date:
2014-02-07 15:03:44 UTC
List:
ruby-core #60561
Issue #9477 has been updated by Akira Tanaka. Status changed from Open to Closed % Done changed from 0 to 100 Applied in changeset r44880. ---------- * lib/resolv.rb: Ignore name servers which cause EAFNOSUPPORT on socket creation. Reported by Bjoern Rennhak. [ruby-core:60442] [Bug #9477] ---------------------------------------- Bug #9477: Address family not supported by protocol - socket(2) - udp https://bugs.ruby-lang.org/issues/9477#change-45014 * Author: Bjoern Rennhak * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: * ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-linux] * Backport: ---------------------------------------- On a fresh Debian GNU/Linux VServer guest running the latest RVM HEAD I experienced the following error: ``` Exception `LoadError' at /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:169 - LoadError Exception `Errno::EAFNOSUPPORT' at /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:744 - Address family not supported by protocol - socket(2) - udp ERROR: While executing gem ... (Errno::EAFNOSUPPORT) Address family not supported by protocol - socket(2) - udp ``` (Please see gist below for entire stacktrace). After discussion on irc.freenode.org #rvm with mpapis (rvm maintainer) it turns out ``` rvm rubygems latest-2.0 ``` fixes the issue. ```rvm rubygems head``` did not work. Not quite sure what went wrong here and if this affects anyone who isn't running vserver. Reference: https://gist.github.com/anonymous/483c42ce132495271fc2 https://github.com/rubygems/rubygems/issues/803#issuecomment-33835128 -- http://bugs.ruby-lang.org/