[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>
I would like to request developers meeting around April 17 or 18 in this mo=
14 messages
2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014
— Urabe Shyouhei <shyouhei@...>
2014/04/03
It's good if we have a meeting then.
[#61826] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/03
Regarding openssl issues, I=E2=80=99ve discussed possible meeting time with=
[#61833] Re: Plan Developers Meeting Japan April 2014
— Martin Bo煬et <martin.bosslet@...>
2014/04/03
Hi,
[#61847] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/03
Martin Boテ殕et <martin.bosslet@gmail.com> wrote:
[#61849] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I will post summary of meeting on Google docs after the meeting.
[#61852] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/04
Zachary Scott <e@zzak.io> wrote:
[#61860] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I=E2=80=99m ok with redmine, thanks for bringing up your concern!
[#62076] Candidacy to 2.1 branch maintainer. — Tomoyuki Chikanaga <nagachika00@...>
Hello,
7 messages
2014/04/17
[#62078] Re: Candidacy to 2.1 branch maintainer.
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/04/17
> And does anyone have counter proposal for 2.1 maintenance?
[ruby-core:62236] [Backport200 - Backport #9649] [Closed] Segfault running thread_safe torture tests under Ruby 2.0
From:
usa@...
Date:
2014-04-30 06:05:24 UTC
List:
ruby-core #62236
Issue #9649 has been updated by Usaku NAKAMURA. Status changed from Open to Closed see r44150. ---------------------------------------- Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0 https://bugs.ruby-lang.org/issues/9649#change-46385 * Author: Charles Nutter * Status: Closed * Priority: Normal * Assignee: ---------------------------------------- We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32 It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI. I have not received any reports of segfaults other than this one. -- https://bugs.ruby-lang.org/