Misc #17811: DevelopersMeeting20210521Japan

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2021/05/21 13:00-17:00
Place/Sign-up/Agenda/Log: https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20210521Japan.md

• Dev meeting IS NOT a decision-making place. All decisions should be done at the bug tracker.
• Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
• Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
• We will write a log about the discussion to a file or to each ticket in English.
• All activities are best-effort (keep in mind that most of us are volunteer developers).
• The date, time and place are scheduled according to when/where we can reserve Matz's time.
• DO NOT discuss then on this ticket, please.

Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)

Example:

* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.

• It is recommended to add a comment by 2021/05/18. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
• The format is strict. We'll use this script to automatically create an markdown-style agenda. We may ignore a comment that does not follow the format.
• Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion.

[mame (Yusuke Endoh)]

• Related to Misc #14770: [META] DevelopersMeeting added

[jeremyevans0 (Jeremy Evans)]

• [Bug #15928] Constant declaration does not conform to JIS 3017:2013 (jeremyevans0)
  • Do we want to make constant assignment evaluation similar to attribute assignment (e.g. use left-to-right evaluation)?
  • We recently made a similar change to make multiple assignment use left-to-right evaluation (#4443), and I think constant assignment should operate the same way.
• [Bug #17767] Cloned ENV inconsistently returns ENV or self (jeremyevans0)
  • How should ENV.dup and ENV.clone work?
  • I propose to have them return ENV, since they share the same storage.
  • If we do want ENV.dup and ENV.clone to return ENV, is the patch acceptable?
• [Bug #13876] Tempfile's finalizer can be interrupted by a Timeout exception which can cause the process to hang (jeremyevans0)
  • Currently, exceptions can be raised during finalizer processing (in GC context), causing process hangs.
  • Can we mark when a thread is running finalizers and not check for pending interrupts in that case, as the patch does?
• [Bug #17739] Array#sort! changes the order even if the receiver raises FrozenError in given block (jeremyevans0)
  • Currently, freezing an array inside Array#sort! allows further changes to the array.
  • Should we prevent further changes to the array by checking whether the array is frozen each time the block returns?
• [Bug #17631] Numeric#real? incorrectly returns true for NaN and INFINITY (jeremyevans0)
  • Is the current behavior of real? and complex? expected, where Complex#real? is always false and Numeric#real? is always true?
  • I believe so and think this bug should be closed, but I would like to get confirmation.

[byroot (Jean Boussier)]

• [Feature #17795] Around Process.fork callbacks API
  • Was considered in the last meeting, but didn't reach any conclusion
  • Since then more use cases and argument were brought.
• [Feature #16038] Provide a public WeakMap that compares by equality rather than by identity
  • Would allow user code to implement interned value objects, similar to String#-@ but for arbitrary types.
  • Was initially proposed about 2 years ago, but didn't reach a conclusion.

[duerst (Martin Dürst)]

• [Feature #17849] Fix Timeout.timeout so that it can be used in threaded Web servers
  • Ruby is used a lot in Web servers and other places with Threads and potential timeouts.
  • We should make sure we can provide the best possible timeout solution for these environments.

[alanwu (Alan Wu)]

• [Bug #17822] Inconsistent visibility behavior with refinements (alanwu)
  • I think the three cases in the repro script should behave the same. What do you think?
  • If they should behave the same, what should be that behavior?

[ko1 (Koichi Sasada)]

• [Feature #17863] rewrite lib/debug.rb with latest API (ko1)
  • Please confirm APIs (file name, method name, etc)

[sam.saffron (Sam Saffron)]

• [Bug #17781] Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang

  • Security issue is quite severe (can cause denial of service), any chance we can do a 2.7.4 release shortly?

[hsbt (Hiroshi SHIBATA)]

• [Feature #17873] Update of default gems in Ruby 3.1
  • Does anyone have any objections?

[mame (Yusuke Endoh)]

• Description updated (diff)

[mame (Yusuke Endoh)]

• Status changed from Open to Closed