From: "byroot (Jean Boussier) via ruby-core" Date: 2024-04-03T08:00:07+00:00 Subject: [ruby-core:117424] [Ruby master Misc#20336] DevMeeting-2024-04-17 Issue #20336 has been updated by byroot (Jean Boussier). * [Feature #20396] Add `string_value: true/false` parameter to `ObjectSpace.dump_all` (byroot) * This method is often used in production to investigate memory leak and other memory related issues. * Because it dumps (pure ASCII) strings content, it may include personal identifiable information, secret keys, etc. * I'd like a mode that doesn't dump the string content to make it easier and safer to use in production. * I'd like to make this new mode the default to avoid mistakes. The backward compatibility concern should be minimal because string content is already optional. * [Feature #20335] `Thread.each_caller_location` should accept the same arguments as `caller` and `caller_locations` (byroot) * When walking up the stack to find a specific frame, it's extremely common to want to skip the first one or two frames (see links in original issue), so I'd like an optional `start` argument. * @Eregon pointed that the `length` and `range` arguments wouldn't be useful, which I agree with, so perhaps they shouldn't be added. ---------------------------------------- Misc #20336: DevMeeting-2024-04-17 https://bugs.ruby-lang.org/issues/20336#change-107799 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2024/04/17 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/04/14. 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/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/