[#30995] [Bug #3523] win32 exception c0000029 on exit using fibers — B Kelly <redmine@...>

Bug #3523: win32 exception c0000029 on exit using fibers

19 messages 2010/07/02

[#31100] [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...>

Hello,

26 messages 2010/07/07
[#31148] Re: [rubysoc] Queue C-extension patch to come — Roger Pack <rogerdpack2@...> 2010/07/09

> As this it my first patch to Ruby, I don't know where to begin with.

[#31320] Re: [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...> 2010/07/16

Sorry for leaving this thread for so long. I've tried to finish the

[#31322] Re: [rubysoc] Queue C-extension patch to come — Aaron Patterson <aaron@...> 2010/07/16

On Sat, Jul 17, 2010 at 06:55:35AM +0900, Ricardo Panaggio wrote:

[#31324] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

NB: I am Ricardo's mentor for this project.

[#31331] Re: [rubysoc] Queue C-extension patch to come — Benoit Daloze <eregontp@...> 2010/07/17

On 17 July 2010 06:00, Caleb Clausen <vikkous@gmail.com> wrote:

[#31332] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

On 7/17/10, Benoit Daloze <eregontp@gmail.com> wrote:

[#31138] Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...>

Hi!

14 messages 2010/07/08
[#31146] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 7:04), Nikolai Weibull wrote:

[#31149] Re: Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...> 2010/07/09

On Fri, Jul 9, 2010 at 06:20, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#31150] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 18:28), Nikolai Weibull wrote:

[#31217] [Bug #3562] regression in respond_to? — Aaron Patterson <redmine@...>

Bug #3562: regression in respond_to?

14 messages 2010/07/12

[#31269] [Bug #3566] memory leak when spawning+joining Threads in a loop — Eric Wong <redmine@...>

Bug #3566: memory leak when spawning+joining Threads in a loop

14 messages 2010/07/13

[#31399] [Backport #3595] Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string — Dreamcat Four <redmine@...>

Backport #3595: Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string

17 messages 2010/07/21

[#31459] [Bug #3607] [trunk/r28731] Gem.path has disappeared? — Ollivier Robert <redmine@...>

Bug #3607: [trunk/r28731] Gem.path has disappeared?

22 messages 2010/07/23

[#31519] [Bug #3622] Net::HTTP does not wait to send request body with Expect: 100-continue — Eric Hodel <redmine@...>

Bug #3622: Net::HTTP does not wait to send request body with Expect: 100-continue

9 messages 2010/07/28

[ruby-core:31206] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9

From: Evan Phoenix <evan@...>
Date: 2010-07-12 07:41:06 UTC
List: ruby-core #31206
On Jul 11, 2010, at 9:13 AM, Yusuke ENDOH wrote:

> Hi,
> 
> 2010/7/12 Luis Lavena <luislavena@gmail.com>:
>> On Sun, Jul 11, 2010 at 12:26 PM, Yusuke ENDOH <mame@tsg.ne.jp> wrote:
>>> Uh-oh, rc2 has been released.
>>> This issue entered a more difficult phase...
>>> 
>>> 
>> 
>> This means that Evan Phoenix fix hasn't been integrated?
> 
> Yes.
> 
> 
>> That is a terrible news, considering that Roger Pack's report was
>> highly unlikely be related or associated with Evan's fix.
> 
> Agreed.  But unless the problem is reported without the fix, we can't
> help but be conservative to include the fix.

This is very bad news. This fix effects a lot of people. I did not respond because Roger indicate he could not reproduce it himself. No one has been able to reproduce the issue, including Roger himself. If that is the reason the fix did not make it into 1.9.2, that's very sad.

> 
> 
>> Where we can see the schedule of releases? Aiming in the future not
>> miss those deadlines with critical things that could be problematic
>> for lot of developers.
> 
> http://redmine.ruby-lang.org/wiki/ruby-19/ReleasePlan
> 
> Originally, rc1 had been the last chance to include the patch with
> public preview.  But Yugui planned to release rc2 to spare us some
> time for some issues.  We missed the true last chance.
> 
> 
> I talked with Yugui a few minutes, and
> 
>  - she had had no reluctance to include the fix if it is dependable
>    (but I don't know whether she will accept the fix even after rc2)
> 
>  - she didn't think this issue was serious because it could be
>    worked around by using bundler (? I'm not sure that I understand
>    her opinion precisely)

This is exactly backwards from what I understand. This bug means that bundler can not run on 1.9.2, and thus rails 3.0 can not run on 1.9.2. This is what Yehuda has told me.

If 1.9.2 can not support rails 3, I fear that the ruby community will reject 1.9.2 right away. I ask that matz, yugui, and all ruby-core developers consider this before allowing the bug to go unfixed.

The pace of this bug has frustrated everyone, please don't let it die now.

 - Evan

> 
> -- 
> Yusuke Endoh <mame@tsg.ne.jp>
> 
> 


In This Thread