[#90399] [Ruby trunk Feature#14813] [PATCH] gc.c: make gc_enter+gc_exit pairs dtrace probes, too — ko1@...
Issue #14813 has been updated by ko1 (Koichi Sasada).
3 messages
2018/12/10
[#90417] [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD — naruse@...
Issue #15398 has been reported by naruse (Yui NARUSE).
4 messages
2018/12/11
[#90423] Re: [Ruby trunk Bug#15398] TestThread#test_signal_at_join fails on FreeBSD
— Eric Wong <normalperson@...>
2018/12/11
naruse@airemix.jp wrote:
[#90519] Spoofing warnings for mail from bugs.ruby-lang.org — Charles Oliver Nutter <headius@...>
I'm getting a spoofing warning for emails sent from bugs.ruby-lang.org when
4 messages
2018/12/13
[#90522] Re: Spoofing warnings for mail from bugs.ruby-lang.org
— Eric Wong <normalperson@...>
2018/12/13
Charles Oliver Nutter <headius@headius.com> wrote:
[#90533] [Ruby trunk Feature#15413] unmarkable C stack (3rd stack) — normalperson@...
Issue #15413 has been reported by normalperson (Eric Wong).
3 messages
2018/12/14
[#90581] [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception — mat999@...
Issue #15424 has been reported by splitice (Mathew Heard).
3 messages
2018/12/17
[#90595] [Ruby trunk Bug#15430] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been reported by hsbt (Hiroshi SHIBATA).
3 messages
2018/12/18
[#90614] [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI — hsbt@...
Issue #15430 has been updated by hsbt (Hiroshi SHIBATA).
4 messages
2018/12/19
[#90630] Re: [Ruby trunk Bug#15430][Assigned] test_fork_while_parent_locked is failing status on Ruby CI
— Eric Wong <normalperson@...>
2018/12/20
> It still exists. https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20181218T230003Z.fail.html.gz
[#90820] Re: [ruby-cvs:73697] k0kubun:r66593 (trunk): accept_nonblock_spec.rb: skip spurious failure — Eric Wong <normalperson@...>
k0kubun@ruby-lang.org wrote:
3 messages
2018/12/30
[ruby-core:90699] [Ruby trunk Misc#15459] Developers Meeting before/after RubyKaigi2019
From:
ko1@...
Date:
2018-12-25 08:39:55 UTC
List:
ruby-core #90699
Issue #15459 has been reported by ko1 (Koichi Sasada).
----------------------------------------
Misc #15459: Developers Meeting before/after RubyKaigi2019
https://bugs.ruby-lang.org/issues/15459
* Author: ko1 (Koichi Sasada)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
RubyKaigi 2019 will be at Fukuoka, Apr 18th to 20th 2019. It should be good time to gather Ruby interpreter developers.
I keep the meeting space at Fukuoka city, near to the Hakata station (the central station in Fukuoka) before and after RubyKaigi.
* Date:
* 2019/04/17 (Wed), before RubyKaigi2019
* 2019/04/21 (Sun), after RubyKaigi2019
* Location
* Fukuoka Ruby Content Industry Promotion Center,
Fukuoka Higashi Sougouchousha 5th floor,
1 Chome-17-1 Hakataekihigashi, Hakata Ward, Fukuoka
* 福岡県Ruby・コンテンツ産業振興センター (in Japanese)
http://frac.jp/about/ (Japanese page)
There are two days but Matz can only attend Wednesday.
Maybe on Wednesday we can have a meeting with agenda, for example about Ruby 3.
I'm not sure we need Sunday meetup, but I keep a room for people who want to continue development.
If nobody attend Sunday meetup, I'll cancel room reservation.
I hope we can discuss topics on Wed and continue to discuss RubyKaigi days, and make a progress on Sunday.
## Travel support
Same as last RubyKaigi, Cookpad Inc. will support travel fee (except hotel room fee) so please consider to attend this dev-meeting.
Also please invite people who are not a MRI committer but who are important person to talk with us.
I'll announce about this travel support soon.
## Registration
* Sign-up on https://rubyassociation.doorkeeper.jp/events/85108
## Call for Topics
* Please comment discussion topics on Wed meeting.
* We have limited time to discuss, so that I'll ask Matz which topics we should talk with, and make time schedule in advance if there are many topics.
* Meeting room has a projector so you can bring your slides.
* Maybe attendee's topics will be prioritize.
## Conclusion
Anyway, please keep your schedule.
FYI: Fukuoka city does not have enough hotel rooms so I recommend you to keep your rooms as soon as possible.
Thanks,
Koichi
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>