Issue #20574 has been updated by jeremyevans0 (Jeremy Evans). * [Bug #20505] Reassigning the block argument in method body keeps old block when calling super with implicit arguments (jeremyevans0) * This makes behavior when reassigning block argument inconsistent with reassigning positional/keyword arguments. * Do we want to make any changes here? * [Bug #19266] URI::Generic should use URI::RFC3986_PARSER instead of URI::DEFAULT_PARSER (jeremyevans0) * This allows URI::Generic.build to accept hostnames with underscores. * This will also fix #19756. * RFC 3986 is almost 20 years old now. * There is an open pull request to uri to implement this change that passes all uri tests. * Can the pull request be merged? * [Bug #9115] Logger traps all exceptions; breaks Timeout (jeremyevans0) * I know logger is moving out of stdlib, but it would be nice to fix this before then. * There is an almost 5-year old backwards-compatible pull request that supports not swallowing given exception classes. * An alternative, less backwards-compatible approach would be to only rescue IOErrors. * No response from the logger maintainer in the last 4 years. * Can we make a decision on how to handle this? ---------------------------------------- Misc #20574: DevMeeting-2024-07-11 https://bugs.ruby-lang.org/issues/20574#change-108964 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2024/07/11 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 2024/07/08. 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/