Issue #19240 has been updated by jeremyevans0 (Jeremy Evans). * [Feature #19347] Add Dir.fchdir (jeremyevans0) * This method is useful when passing directory file descriptors through UNIX sockets or to child processes to avoid TOCTOU vulnerabilities. * We already have Dir#fileno, but nothing that can use the returned directory file descriptor. * Is it OK to add this method? * If so, is the implementation in the pull request acceptable? * [Bug #19237] Hash default_proc is not thread-safe to lazy-initialize value for a given key (jeremyevans0) * Similar to `hash[key] ||= value` in multiple concurrent threads. * One workaround is using a Mutex and `mutex.synchronize{hash[key] = value unless hash.key?(key)}` inside the default proc. * Another workaround is to avoid using a default proc to set values in a hash accessed by multiple concurrent threads. * Is this a bug? If not, should we update the documentation of `Hash.new` and/or `Hash#default_proc=` regarding use with concurrent threads? * [Bug #19286] What should kwargs' arity be? (jeremyevans0) * Do we want to change how arity is calculated for methods/procs accepting/requiring keywords? * I don't think it is worth breaking backwards compatibility here (#parameters can be used for keyword argument details). * [Bug #19293] The new Time.new(String) API is nice... but we still need a stricter version of this (jeremyevans0) * Do we want to add a keyword argument to Time.new for stricter parsing, or another Time method that is stricter? ---------------------------------------- Misc #19240: DevMeeting-2023-01-19 https://bugs.ruby-lang.org/issues/19240#change-101254 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2023/01/19 13:00-17:00** (JST) Log: *TBD* - 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 record of the discussion in the 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 of the meeting 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 2023/01/16. 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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- https://bugs.ruby-lang.org/