[#59462] [ruby-trunk - Bug #9342][Open] [PATCH] SizedQueue#clear does not notify waiting threads in Ruby 1.9.3 — "jsc (Justin Collins)" <redmine@...>

9 messages 2014/01/02

[#59466] [ruby-trunk - Bug #9343][Open] [PATCH] SizedQueue#max= wakes up waiters properly — "normalperson (Eric Wong)" <normalperson@...>

11 messages 2014/01/02

[#59498] [ruby-trunk - Bug #9352][Open] [BUG] rb_sys_fail_str(connect(2) for [fe80::1%lo0]:3000) - errno == 0 — "kain (Claudio Poli)" <claudio@...>

10 messages 2014/01/03

[#59516] [ruby-trunk - Bug #9356][Open] TCPSocket.new does not seem to handle INTR — "charliesome (Charlie Somerville)" <charliesome@...>

48 messages 2014/01/03

[#59538] [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — "shyouhei (Shyouhei Urabe)" <shyouhei@...>

33 messages 2014/01/03
[#59582] Re: [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — SASADA Koichi <ko1@...> 2014/01/06

Intersting challenge.

[#59541] Re: [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — Eric Wong <normalperson@...> 2014/01/04

Hi, I noticed a trivial typo in array.c, and it fails building struct.c

[#59583] [ruby-trunk - Bug #9367][Open] REXML::XmlDecl doesn't use user specified quotes — "bearmini (Takashi Oguma)" <bear.mini@...>

12 messages 2014/01/06

[#59642] [ruby-trunk - Bug #9384][Open] Segfault in ruby 2.1.0p0 — "cbliard (Christophe Bliard)" <christophe.bliard@...>

11 messages 2014/01/08

[#59791] About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...>

A while ago I created a proof-of-concept that I intended to use in my

16 messages 2014/01/15
[#59794] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/15

On 15 Jan 2014, at 11:58, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[#59808] Re: About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2014/01/16

Em 15-01-2014 19:42, Eric Hodel escreveu:

[#59810] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/16

On 16 Jan 2014, at 02:15, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[#59826] Re: About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2014/01/17

Em 16-01-2014 19:43, Eric Hodel escreveu:

[#59832] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/17

On 17 Jan 2014, at 04:22, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[ruby-core:59733] Re: Ruby 2.1.0 in Production: known bugs and patches

From: "Martin J. Dürst" <duerst@...>
Date: 2014-01-13 03:54:41 UTC
List: ruby-core #59733
Hello Aman,

Many thanks for your report. Great news about Ruby 2.1.

Today is a holiday in Japan, so responses may not be that quick (or they 
may be quicker because people don't have to go to work and can hack on 
Ruby all day :-).

If you have some time, can you try to reopen the issues affected, with 
settings changed similar to 
https://bugs.ruby-lang.org/issues/9168#note-5 (please set assignee to 
Yui NARUSE).

Re. issuing a 2.1.1 release sooner rather than later, last Friday at a 
small meeting/party to discuss and celebrate the 2.1 release (see , 
sorry, in Japanese) we discussed the idea of publishing a 2.1.x release 
about every three months, but earlier if there is a good set of 
important patches. Your list may be just that.

Re. the performance patches, you recommend them for large ruby apps. 
What about small apps?

Regards,    Martin.

On 2014/01/13 11:29, Aman Gupta wrote:
> Last week, we upgraded the github.com rails app to ruby 2.1.0 in production.
> While testing the new build for rollout, we ran into a number of bugs. Most
> of
> these have been fixed on trunk already, but I've documented them below to
> help
> anyone else who might be testing ruby 2.1 in production.
>
> @naruse I think we should backport these patches to the ruby_2_1 branch and
> release 2.1.1 sooner rather than later, as some of the bugs are quite
> critical.
> I'm happy to offer any assistance I can to expedite this process.
>
> - Struct#send(:setter=, rhs) does not return rhs
>    #9353 (r44501)
>    breaks the faraday gem
>
> - Array#uniq behavior change
>    #9340 (r44512)
>    affects the sass gem
>
> - Timeout behavior change
>    #9354 (r44517, r44518, r44519)
>    #9380 (r44523)
>    breaks the faraday gem
>
> - [BUG] assertion failure in socket.c
>    #9352 (r44490, r44496)
>    breaks the excon gem
>
> - segfault in method() usage
>    #9334, #9313, #9310, #9326, #9337
>    #9315 (r44455, r44458, r44510, r44527, r44552, r44553)
>    segv inside activesupport4 and other gems
>
> - Hash lookup with #hash and #eql broken
>    #9381 (r44525, r44534, r44537)
>
> - bigdecimal division issue
>    #9316
>    affects some payment processing gems
>    workaround patch by @phasis:
>      https://github.com/github/ruby/commit/1e778b3b20
>
> - SizedQueue not working
>    #9302, #9343, #9396
>    patches by @normalperson:
>      https://bugs.ruby-lang.org/attachments/download/4113
>      https://bugs.ruby-lang.org/attachments/download/4140
>
> In addition to the bugfix patches above, we're running the following
> performance patches in production. These have proven quite stable in our
> environment, so I encourage you to try them if you're running a large ruby
> app.
>
> - funny-falcon's st.c density patch
>    https://github.com/github/ruby/commit/1e025cbd2f
>
> - funny-falcon's st.c pool allocator
>    https://github.com/github/ruby/commit/3d37e2b5a3
>
> - funny-falcon's method cache patch
>    https://github.com/funny-falcon/ruby/compare/trunk...class_local_cache
>    proposed for trunk in #9262
>
> - optimized Hash#[] and Hash#[]= with string literals
>    https://github.com/github/ruby/commit/86946e72d7
>    merged to trunk in #9382 (r44551)
>
> Aside from the bugs above, our upgrade to 2.1 was very smooth. I'm happy to
> report that github.com is now running faster (and with less GC overhead)
> than
> ever before.
>
>    Aman
>

In This Thread