[#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:31240] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9

From: Evan Phoenix <evan@...>
Date: 2010-07-13 05:57:12 UTC
List: ruby-core #31240
On Jul 12, 2010, at 8:27 PM, Yusuke ENDOH wrote:

> 2010/7/13 Yehuda Katz <redmine@ruby-lang.org>:
>> If the problem is that ruby-core doesn't use RubyGems that much, and isn't willing to avoid breaking fundamental package manager properties, perhaps it's worth reconsidering including it in Ruby 1.9.
> 
> Agreed.
> 
> 
> BTW, I don't see why you did not complain until rc1 is released.
> I gave and noticed you a chance to test your product [ruby-core:30543].
> In addition, the preview plan was announced in May [ruby-core:28665].

I'm sorry that I got involved in the situation so late. Yehuda and Aaron Patterson both approached me about the problem not long ago.

> 
> In fact, I heard from Shyouhei that you had noticed some trouble about
> this issue in June (though I cannot know the detail because you did
> not complain formally).

I'm unable to speak about how or when the bug was seen in the past, but regardless, it did go overlooked for too long. All we can do now is correct the situation.

> 
> You actually had a chance.  In this case, I can't help but say that you
> are too uncooperative, or even opposing to 1.9.2 release.  This result
> is what you asked for.
> 
> In this case I guess we could manage this issue, thanks to Evan's patch.
> But, please please cooperate us in next time.

I asked Eric to official appoint me as the maintainer of gem_prelude so that future issues related to it can be handled swiftly. I'm happy to fulfill this duty.

My hope is that my patch goes into 1.9.2, and on trunk we can further refine the solution. In the coming weeks, I'll be asking ruby-core for input on what the core features of gem_prelude must be so that we can accomplish that goal without problems.

Yusuke, thank you for your patience in dealing with this bug. I know that it has cause d the 1.9.2 release process and you much grief, but I think we all now agree that fixing the bug in some way is necessary for 1.9.2.

Your humble gem_prelude maintainer,
  Evan Phoenix


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


In This Thread