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

From: Yusuke ENDOH <mame@...>
Date: 2010-07-13 03:38:32 UTC
List: ruby-core #31236
Hi,

2010/7/13 Yukihiro Matsumoto <matz@ruby-lang.org>:
> I am sorry that I haven't followed this issue.  As far as I
> understand, this is caused by unfortunate timing.  Eric was busy at
> the critical timing

Not only at that timing.  He is always busy.

[ruby-core:28689] [ruby-core:28781] [ruby-core:28926]
[ruby-core:30127] [ruby-core:30129] [ruby-core:30130]
[ruby-core:30151] [ruby-core:30189] [ruby-core:30456]
[ruby-core:30619] [ruby-core:30621] [ruby-core:30792]
[ruby-core:30907]

Of course I can't blame his busyness, but looking objectively,
he looks like ineligible for a maintainer.


> I think 1.9.2 should run Rails3.

I hope too.  I wanted them to know the very poor maintenance status
of rubygems and to do it themselves, as they are beneficiaries.

OTOH there are also many people who wait for 1.9.2 but don't need
rubygems nor rails.


> If I understand what Yehuda told me
> correctly, this issue could be a show stopper.

I don't agree to see the issue as a show stopper unless some active
developer is assigned to the issue.  Otherwise it would take forever,
literally.


In practice, I think Evan's patch is a meeting point, if Roger can
confirm the [BUG] does not occur on ruby_1_9_2 with Evan's patch.
If it does not occur on ruby_1_9_2, I also suspect it is due to lazy
sweep ([ruby-core:31228]).

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

In This Thread