- ruby-core - ml.ruby-lang.org

[ruby-core:125062] [Ruby Misc#21956] DevMeeting-2026-05-13
by mame (Yusuke Endoh) 12 May '26

12 May '26

Issue #21956 has been reported by mame (Yusuke Endoh). ---------------------------------------- Misc #21956: DevMeeting-2026-05-13 https://bugs.ruby-lang.org/issues/21956 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2026/05/13 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 2026/05/10. 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/

6 6

[ruby-core:125470] [Ruby Feature#22066] MemoryView feedbacks: error reporting and lack of formats
by KitaitiMakoto 12 May '26

12 May '26

Issue #22066 has been reported by KitaitiMakoto (真北市). ---------------------------------------- Feature #22066: MemoryView feedbacks: error reporting and lack of formats https://bugs.ruby-lang.org/issues/22066 * Author: KitaitiMakoto (真北市) * Status: Open ---------------------------------------- Hello. I have been doing small-scale development involving MemoryView for the past two or three years, and I would like to report two use cases I encountered. ## No way to communicate the reason for failure `rb_memory_view_get_func_t` returns `false` when there is a problem, but it would be helpful if the type of problem could also be communicated to the caller - for example, whether the requested flags are not supported, or whether there is an issue with the object's state. In Ruby, exceptions are normally used for this purpose. However, as far as I understand, `rb_memory_view_get_func_t` is currently designed as a boolean-returning function, and there is no documented way to return a structured failure reason while still returning `false`. Currently I output the problem with `rb_warn` before returning `false`. Would it be possible to add an output parameter for an exception, for example: ```c typedef bool (* rb_memory_view_get_func_t)(VALUE obj, rb_memory_view_t *view, int flags); | v typedef bool (* rb_memory_view_get_func_t)(VALUE obj, rb_memory_view_t *view, int flags, VALUE *error); ``` or, add a member function to retrieve the error? ## Insufficient format support When I tried to export GStreamer gem data as a MemoryView, I found that some formats were missing. [GStreamer supports formats such as 24-bit little-endian integers](https://gstreamer.freedesktop.org/documentation/audio/audio-forma… (S24LE), but these could not be expressed using MemoryView's format strings. The size alone can be represented by combining existing format characters like `ccc`, but the semantics are different. Furthermore, there are formats such as `S24_32LE`, where the storage width is 32 bits but the valid bit depth is 24 bits. This also cannot be expressed in the current MemoryView specification. I don't use these formats myself, and since GStreamer appears to be defined quite broadly, I suspect others don't use them much either - but I'm reporting the limitation as a fact. Would it be feasible to either add new format strings, or to express item characteristics using a combination of sign, type, size, and endianness (such as S24LE)? --- As I have only been working in this area in a limited and intermittent way, these proposals may be narrow in perspective, but I hope they can be of some reference for future development. Please feel free to ask if anything needs more detail. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:124843] [Ruby Misc#21916] DevMeeting before RubyKaigi 2026
by ko1 (Koichi Sasada) 12 May '26

12 May '26

Issue #21916 has been reported by ko1 (Koichi Sasada). ---------------------------------------- Misc #21916: DevMeeting before RubyKaigi 2026 https://bugs.ruby-lang.org/issues/21916 * Author: ko1 (Koichi Sasada) * Status: Open ---------------------------------------- RubyKaigi 2026 will be at Hakodate, Japan, Apr 22th - 24th. We would like to try to hold a face-to-face dev meeting at Hakodate. (@matz will also participate!) * Date: 2026/04/21 (Tue.) 15:00-17:00 (The day before RubyKaigi) * Location: RubyKaigi venue (detailed will be announced before the meeting) ### How to participate Open to any RubyKaigi attendees who have a commit bit or who have a topic they particularly want to discuss. Please sign up on the doorkeeper page: https://rubyassociation.doorkeeper.jp/events/195298 The meeting will be held in a hackathon event. Please enjoy Ruby hacking with friends if you want before the meeting. Note: Do not forget to register RubyKaigi ticket too (see "[ruby-core:124591] Invitation to RubyKaigi 2026" from Akira). ### Program * 11:00am door open and start the Hackathon event * 3:00pm opening and self introduction * 3:30pm discuss topics * 5:00pm closing and free time (closing time is depends on topics) * 6:00pm door close ### 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 2025/04/20. I'll ask Matz which should be discussed on this meeting and reorder them. - 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/

6 6

[ruby-core:125465] [Ruby Bug#22002] argument stack underflow (-1)
by k0kubun (Takashi Kokubun) 11 May '26

11 May '26

Issue #22002 has been updated by k0kubun (Takashi Kokubun). Backport changed from 3.3: DONTNEED, 3.4: REQUIRED, 4.0: REQUIRED to 3.3: DONTNEED, 3.4: REQUIRED, 4.0: DONE ruby_4_0 commit:a9e4608b5225d665ec9c9353a8350f5b940c20fe merged revision(s) commit:d077df24a2256d760cc534b242b28822d4ef6376. ---------------------------------------- Bug #22002: argument stack underflow (-1) https://bugs.ruby-lang.org/issues/22002#change-117273 * Author: Anonymous * Status: Closed * Assignee: prism * ruby -v: ruby 4.0.1 (2026-01-13 revision e04267a14b) +PRISM [arm64-darwin25] * Backport: 3.3: DONTNEED, 3.4: REQUIRED, 4.0: DONE ---------------------------------------- The following lines of code: ```ruby sleep(0.1) until defined?(@variable) @variable ``` produce this error: ``` home@My-Air testing % bundle exec ruby test.rb -- raw disasm-------- trace: 1 0000 jump <L000> ( 1) <L004> [sp: 0, unremovable: 1, refcnt: 1] 0002 putnil ( 1) <L005> [sp: 1, unremovable: 0, refcnt: 1] 0003 pop ( 1) 0004 jump <L000> ( 1) <L001> [sp: 0, unremovable: 1, refcnt: 5] 0006 putself ( 1) 0007 putobject 0.1 ( 1) 0009 opt_send_without_block <calldata:sleep, 1> ( 1) 0011 pop ( 1) <L000> [sp: 0, unremovable: 0, refcnt: 2] <L012> [sp: 0, unremovable: 0, refcnt: 0] * 0012 branchunless <L001> ( 1) adjust: [label: 4] 0014 putnil ( 1) <L002> [sp: -1, unremovable: 0, refcnt: 4] 0015 pop ( 1) trace: 1 0016 getinstancevariable :@variable, <ivc:0> ( 3) 0019 leave ( 3) --------------------- test.rb:1: argument stack underflow (-1) test.rb: compile error (SyntaxError) ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:125279] [Ruby Bug#22004] parse.y doesn't executes loop body with `while true || true` condition
by Earlopain (Earlopain _) 11 May '26

11 May '26

Issue #22004 has been reported by Earlopain (Earlopain _). ---------------------------------------- Bug #22004: parse.y doesn't executes loop body with `while true || true` condition https://bugs.ruby-lang.org/issues/22004 * Author: Earlopain (Earlopain _) * Status: Open * ruby -v: ruby 4.1.0dev (2026-04-15T13:47:25Z master d077df24a2) +PRISM [x86_64-linux] * Backport: 3.3: WONTFIX, 3.4: REQUIRED, 4.0: REQUIRED ---------------------------------------- ```rb while true || true puts 1 end ``` This should never exit but with parse.y, the body is never executed. It seems to happen when one of the conditions is a truthy literal. Something similar happens with `unitl`: ```rb until false && true puts 1 end ``` By moving the literals out to methods that just return them, it behaves like I would expect. Seems to have started happening in Ruby 3.3. -- https://bugs.ruby-lang.org/

3 2

[ruby-core:124918] [Ruby Bug#21940] Ruby::Box: `$_` returns stale value due to gvar_tbl caching
by dak2 (Daichi Kamiyama) 11 May '26

11 May '26

Issue #21940 has been reported by dak2 (Daichi Kamiyama). ---------------------------------------- Bug #21940: Ruby::Box: `$_` returns stale value due to gvar_tbl caching https://bugs.ruby-lang.org/issues/21940 * Author: dak2 (Daichi Kamiyama) * Status: Open * ruby -v: 4.0.1 * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- ## Environment - Ruby Version v4.0.1 - OS: macOS 15.6.1 (arm64) - `RUBY_BOX=1` enabled ## Reproduction ```shell echo -e "a\nb" | RUBY_BOX=1 ruby -e 'gets; $_; gets; p $_' ``` ## Expected ``` "b\n" ``` The second gets reads `"b"` and sets it to `$_`. `p $_` should return the latest value. ## Actual ``` "a\n" ``` `$_` returns the stale value from the first gets. ## Root Cause `$_` is a special variable stored in `svar`. Its getter (`rb_lastline_get`) reads the current value from svar each time it is called. However, when Box is enabled, I believe `rb_gvar_get()` caches the value in the Box's `gvar_tbl` on first access. On subsequent reads, it returns the cached value directly without calling the getter. Since gets updates `$_` via `rb_lastline_set()` which bypasses `rb_gvar_set()`, the cache becomes stale. -- https://bugs.ruby-lang.org/

3 4

[ruby-core:125456] [Ruby Bug#22063] Regexp timeout accepts NaN and disables timeout
by afurm (Andrii Furmanets) 11 May '26

11 May '26

Issue #22063 has been reported by afurm (Andrii Furmanets). ---------------------------------------- Bug #22063: Regexp timeout accepts NaN and disables timeout https://bugs.ruby-lang.org/issues/22063 * Author: afurm (Andrii Furmanets) * Status: Open * ruby -v: ruby 4.1.0dev (2026-05-11T07:56:09Z master d0ea61cb87) +PRISM [arm64-darwin25] * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- `Regexp.timeout=` and `Regexp.new(..., timeout:)` currently accept `Float::NAN`. The value passes the positive-timeout validation because `NaN <= 0` is false, and then `double2hrtime` stores it as a zero timeout value. This makes both APIs behave as if no timeout was configured: ```ruby p Regexp.new("foo", timeout: Float::NAN).timeout #=> nil Regexp.timeout = Float::NAN p Regexp.timeout #=> nil ``` `Float::NAN` is not a valid positive timeout value, so I expect it to raise `ArgumentError`, the same as `0` and negative values. Reproduced on master: ```text ruby 4.1.0dev (2026-05-11T07:56:09Z master d0ea61cb87) +PRISM [arm64-darwin25] ``` Proposed fix: Reject NaN in the shared regexp timeout validation helper before converting the double to `rb_hrtime_t`. Pull request: https://github.com/ruby/ruby/pull/16917 -- https://bugs.ruby-lang.org/

2 2

[ruby-core:125458] [Ruby Feature#13677] Add more details to error "Name or service not known (SocketError)"
by chucke (Tiago Cardoso) 11 May '26

11 May '26

Issue #13677 has been updated by chucke (Tiago Cardoso). PR to add this feature: https://github.com/ruby/ruby/pull/16918 . LMK what you think. ---------------------------------------- Feature #13677: Add more details to error "Name or service not known (SocketError)" https://bugs.ruby-lang.org/issues/13677#change-117262 * Author: dsbonev (Dimitar Bonev) * Status: Feedback ---------------------------------------- ruby version: `ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]` ruby script: ~~~ ruby require 'socket' TCPSocket.new 'nonexistent.example.com', 80 ~~~ Result: `getaddrinfo: Name or service not known (SocketError)` Expected: `getaddrinfo: Name or service not known for nonexistent.example.com (SocketError)` Why: This will make it easier to resolve errors of this kind by just looking at the logged messages. It is common for production and non-production (development, test) code to connect to different hosts which can produce errors due to wrong configuration. This change will make the ruby stdlib code more consistent as other methods already provide useful error information. Some examples: ~~~ ruby host = 'nonexistent.example.com'; port = 80 Resolv.getaddress host # => Resolv::ResolvError: no address for nonexistent.example.com Socket.getservbyname host # => SocketError: no such service nonexistent.example.com/tcp Net::HTTP.get Struct.new(:hostname, :port, :scheme).new(host, port, 'http') # => SocketError: Failed to open TCP connection to nonexistent.example.com:80 (getaddrinfo: Name or service not known) ~~~ If this issue will be resolved, please add any useful information to the error message in addition to the host. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:125455] [Ruby Bug#22062] Regexp timeout accepts NaN and disables timeout
by afurm (Andrii Furmanets) 11 May '26

11 May '26

Issue #22062 has been reported by afurm (Andrii Furmanets). ---------------------------------------- Bug #22062: Regexp timeout accepts NaN and disables timeout https://bugs.ruby-lang.org/issues/22062 * Author: afurm (Andrii Furmanets) * Status: Open * ruby -v: ruby 4.1.0dev (2026-05-11T07:56:09Z master d0ea61cb87) +PRISM [arm64-darwin25] * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- `Regexp.timeout=` and `Regexp.new(..., timeout:)` currently accept `Float::NAN`. The value passes the positive-timeout validation because `NaN <= 0` is false, and then `double2hrtime` stores it as a zero timeout value. This makes both APIs behave as if no timeout was configured: ```ruby p Regexp.new("foo", timeout: Float::NAN).timeout #=> nil Regexp.timeout = Float::NAN p Regexp.timeout #=> nil ``` `Float::NAN` is not a valid positive timeout value, so I expect it to raise `ArgumentError`, the same as `0` and negative values. Reproduced on master: ```text ruby 4.1.0dev (2026-05-11T07:56:09Z master d0ea61cb87) +PRISM [arm64-darwin25] ``` Proposed fix: Reject NaN in the shared regexp timeout validation helper before converting the double to `rb_hrtime_t`. Pull request: https://github.com/ruby/ruby/pull/16917 -- https://bugs.ruby-lang.org/

1 0

[ruby-core:125454] [Ruby Bug#22061] Regexp timeout accepts NaN and disables timeout
by afurm (Andrii Furmanets) 11 May '26

11 May '26

Issue #22061 has been reported by afurm (Andrii Furmanets). ---------------------------------------- Bug #22061: Regexp timeout accepts NaN and disables timeout https://bugs.ruby-lang.org/issues/22061 * Author: afurm (Andrii Furmanets) * Status: Open * ruby -v: ruby 4.1.0dev (2026-05-11T07:56:09Z master d0ea61cb87) +PRISM [arm64-darwin25] * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- `Regexp.timeout=` and `Regexp.new(..., timeout:)` currently accept `Float::NAN`. The value passes the positive-timeout validation because `NaN <= 0` is false, and then `double2hrtime` stores it as a zero timeout value. This makes both APIs behave as if no timeout was configured: ```ruby p Regexp.new("foo", timeout: Float::NAN).timeout #=> nil Regexp.timeout = Float::NAN p Regexp.timeout #=> nil ``` `Float::NAN` is not a valid positive timeout value, so I expect it to raise `ArgumentError`, the same as `0` and negative values. Reproduced on master: ```text ruby 4.1.0dev (2026-05-11T07:56:09Z master d0ea61cb87) +PRISM [arm64-darwin25] ``` Proposed fix: Reject NaN in the shared regexp timeout validation helper before converting the double to `rb_hrtime_t`. Pull request: https://github.com/ruby/ruby/pull/16917 -- https://bugs.ruby-lang.org/

1 0