Issue #19240 has been updated by kjtsanaktsidis (KJ Tsanaktsidis).
* [Feature #19179] upport parsing SCM_CRED(ENTIALS) messages from ancillary messages
* Various UNIX-y OS's support getting the (e)uid, (e)gid, and pid from unix sockets
- some with a socket option, some with an ancillary message
* Ruby's socket module already has code to parse these, but it's only used for
`Socket::Options#inspect` and `Socket::AncillaryData#inspect`
* I propose enhancing `Socket::Options` and `Socket::AncillaryData` to conveniently
support this functionality where it's available
* [Feature #19144]Ruby should set AI_V4MAPPED | AI_ADDRCONFIG getaddrinfo flags by
default
* Many older and widely-deployed glibc versions have a
[
bug](https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1961697) which can cause a
5-second delay in DNS resolutions when IPv4/IPv6 are both enabled
* When IPv6 is not in use, the AI_ADDRINFO flag to getaddrinfo works around this bug by
not making AAAA requests if the host does not have a useable IPv6 address.
* This bug often shows up in Ruby programs in particular, because Ruby accidentally
overwrites one of the overlapping levels of glibc defaults, and causes AI_ADDRCONFIG to be
unset where it would normally be set by default.
----------------------------------------
Misc #19240: DevMeeting-2023-01-19
https://bugs.ruby-lang.org/issues/19240#change-100989
* 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/