Ruby Issue Tracking System

Today

08:52 AM Ruby Revision 334b4ffa (git): [DOC] Clarify `rb_len_t` entry in NEWS.md

byroot (Jean Boussier)

07:52 AM Ruby Feature #22400: Use rb_long_t for lengths so that String and Array can exceed 2GiB on mswin

@hsbt what's the migration path for C extensions? I don't see a `HAVE_RB_LEN_T`, should we provide one so that extensions can declare:
```c
#ifndef HAVE_RB_LEN_T
typedef long rb_len_t;
typedef unsigned long rb_ulen_t;
#endif
``` byroot (Jean Boussier)

10/08/2026

06:50 PM Ruby Revision 870969b2 (git): [ruby/json] Better defend against `to_s` or `encode` not returning a T_STRING

https://github.com/ruby/json/commit/cdcfdb8066 byroot (Jean Boussier)

10/07/2026

07:57 AM Ruby Feature #22395 (Closed): RubyVM::InstructionSequence.load_from_binary: to optionally accept `file` and `path` arguments

Applied in changeset commit:git|9ce0df671980d669cbab8afc48124c7453897533.
----------
Make ISeq binaries portable
* Make `__FILE__` a frozen core method that return the iseq path.
* Make `load_from_binary` accept `file, path` like compi... byroot (Jean Boussier)

07:57 AM Ruby Feature #17593 (Closed): load_iseq_eval should override the ISeq path

Applied in changeset commit:git|9ce0df671980d669cbab8afc48124c7453897533.
----------
Make ISeq binaries portable
* Make `__FILE__` a frozen core method that return the iseq path.
* Make `load_from_binary` accept `file, path` like compi... byroot (Jean Boussier)

07:57 AM Ruby Revision 9ce0df67 (git): Make ISeq binaries portable

* Make `__FILE__` a frozen core method that return the iseq path.
* Make `load_from_binary` accept `file, path` like compile.
[Feature #17593]
[Feature #22395] byroot (Jean Boussier)

07:49 AM Ruby Feature #22400: Use rb_long_t for lengths so that String and Array can exceed 2GiB on mswin

> Were completely different names considered, such as len?
Also the natural type to go for would be `size_t`, so `rb_size_t` would make more sense than `rb_long_t`? But then there's the sign difference... byroot (Jean Boussier)

10/06/2026

04:13 PM Ruby Bug #22406: Process.fork can leave the child unable to resolve hostnames: getaddrinfo helper threads take glibc's resolver lock after releasing the fork lock

> If that sounds acceptable, I can put this version up as a second PR so the two can be compared.
Yes please do. I think your proposal is fine, but it's always easier to reason about it with the code. byroot (Jean Boussier)

11:56 AM Ruby Bug #22406: Process.fork can leave the child unable to resolve hostnames: getaddrinfo helper threads take glibc's resolver lock after releasing the fork lock

> it would be a problem if they were only joined when a fork happens.
In my mind we're regularly do non blocking join, e.g. whenever we start a new name resolution, or finish one. So it would be self cleaning. byroot (Jean Boussier)

07:38 AM Ruby Bug #22406: Process.fork can leave the child unable to resolve hostnames: getaddrinfo helper threads take glibc's resolver lock after releasing the fork lock

> rework the PR that way if you'd prefer it.
I personally prefer that option, as adding code that depends on things marked as deprecated scares me a bit. But if @mame feels strongly otherwise I'm ok with it. byroot (Jean Boussier)