February 2024 - ruby-core - ml.ruby-lang.org

[ruby-core:116782] [Ruby master Bug#20269] bignum too big to convert into `long' when running String#byteslice on Windows
by simpliandy (Andy Pfister) 16 Feb '24

16 Feb '24

Issue #20269 has been reported by simpliandy (Andy Pfister). ---------------------------------------- Bug #20269: bignum too big to convert into `long' when running String#byteslice on Windows https://bugs.ruby-lang.org/issues/20269 * Author: simpliandy (Andy Pfister) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x64-mingw-ucrt] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Running `String#byteslice` on Ruby 3.3 on Windows results in an error when using any number bigger than 32 bits: ``` "".byteslice(0, 2547483647) (irb):1:in `byteslice': bignum too big to convert into `long' (RangeError) from (irb):1:in `<main>' from <internal:kernel>:187:in `loop' from C:/Ruby33-x64/lib/ruby/gems/3.3.0/gems/irb-1.11.0/exe/irb:9:in `<top (required)>' from C:/Ruby33-x64/bin/irb:33:in `load' from C:/Ruby33-x64/bin/irb:33:in `<main>' ``` It works fine on MacOS: ``` irb(main):001> "".byteslice(0, 2547483647) => "" irb(main):002> exit Andys-MBP:project apf$ ruby -v ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-darwin23] ``` -- https://bugs.ruby-lang.org/

2 2

[ruby-core:116793] [Ruby master Feature#19117] Include the method owner in backtraces, not just the method name
by byroot (Jean Boussier) 16 Feb '24

16 Feb '24

Issue #19117 has been updated by byroot (Jean Boussier). @mame while updating the Rails test suite I noticed we may have a small regression: ```ruby def raise_nested_exceptions raise "First error" rescue begin raise "Second error" rescue raise "Third error" end end raise_nested_exceptions ``` 3.3.0: ``` /tmp/foo.rb:7:in `rescue in rescue in raise_nested_exceptions': Third error (RuntimeError) from /tmp/foo.rb:4:in `rescue in raise_nested_exceptions' from /tmp/foo.rb:1:in `raise_nested_exceptions' from /tmp/foo.rb:11:in `<main>' /tmp/foo.rb:5:in `rescue in raise_nested_exceptions': Second error (RuntimeError) from /tmp/foo.rb:1:in `raise_nested_exceptions' from /tmp/foo.rb:11:in `<main>' /tmp/foo.rb:2:in `raise_nested_exceptions': First error (RuntimeError) from /tmp/foo.rb:11:in `<main>' ``` 3.4-dev: ``` /tmp/foo.rb:7:in 'Object#raise_nested_exceptions': Third error (RuntimeError) from /tmp/foo.rb:4:in 'Object#raise_nested_exceptions' from /tmp/foo.rb:1:in 'Object#raise_nested_exceptions' from /tmp/foo.rb:11:in '<main>' /tmp/foo.rb:5:in 'Object#raise_nested_exceptions': Second error (RuntimeError) from /tmp/foo.rb:1:in 'Object#raise_nested_exceptions' from /tmp/foo.rb:11:in '<main>' /tmp/foo.rb:2:in 'Object#raise_nested_exceptions': First error (RuntimeError) from /tmp/foo.rb:11:in '<main>' ``` The `rescue in` prefixes are gone. I don't think it was intended? ---------------------------------------- Feature #19117: Include the method owner in backtraces, not just the method name https://bugs.ruby-lang.org/issues/19117#change-106816 * Author: byroot (Jean Boussier) * Status: Closed * Priority: Normal * Target version: 3.4 ---------------------------------------- ``` module Foo class Bar def inspect 1 + '1' end end end p Foo::Bar.new ``` This code produce the following backtrace: ``` /tmp/foo.rb:4:in `+': String can't be coerced into Integer (TypeError) from /tmp/foo.rb:4:in `inspect' from /tmp/foo.rb:9:in `p' from /tmp/foo.rb:9:in `<main>' ``` This works, but on large codebases and large backtraces the method name isn't always all that revealing, most of the time you need to open many of the locations listed in the backtrace to really understand what is going on. I propose that we also include the owner name: ``` /tmp/foo.rb:4:in `Integer#+': String can't be coerced into Integer (TypeError) from /tmp/foo.rb:4:in `Foo::Bar#inspect' from /tmp/foo.rb:9:in `Kernel#p' from /tmp/foo.rb:9:in `<main>' ``` I believe that in many case it would allow to much better understand the backtrace without having to jump back and forth between it and the source code. This is inspired by @ivoanjo 's `backtracie` gem: https://github.com/ivoanjo/backtracie -- https://bugs.ruby-lang.org/

1 0

[ruby-core:115864] [Ruby master Feature#20080] Implement #begin_and_end method on Range
by stuyam (Stuart Yamartino) 15 Feb '24

15 Feb '24

Issue #20080 has been reported by stuyam (Stuart Yamartino). ---------------------------------------- Feature #20080: Implement #begin_and_end method on Range https://bugs.ruby-lang.org/issues/20080 * Author: stuyam (Stuart Yamartino) * Status: Open * Priority: Normal ---------------------------------------- Followup Reference: #20027 This feature request is to implement a method called `#begin_and_end` on `Range` that returns an array of the first and last value stored in a range: ```ruby (1..300).begin_and_end #=> [1, 300] first, last = (300..1).begin_and_end first #=> 300 last #=> 1 ``` I believe this would be a great addition to Ranges as they are often used to pass around a single object used to hold endpoints, and this allows easier retrieval of those endpoints. This would allow easier deconstruction into start and end values using array deconstruction as well as a simpler way to serialize to a more primitive object such as an array for database storage. This implementation was suggested by @mame in my initial feature suggestion regarding range deconstruction: https://bugs.ruby-lang.org/issues/20027 This implementation would work similar to how `#minmax` works where it returns an array of two numbers, however the difference is that `#minmax` doesn't work with reverse ranges as @Dan0042 pointed out in the link above: ```ruby (1..42).minmax #=> [1, 42] (42..1).minmax #=> [nil, nil] ``` -- https://bugs.ruby-lang.org/

9 16

[ruby-core:116781] [Ruby master Bug#20268] Segfault in ruby 3.3 Fiber on aarch64 musl (mac m1)
by vasfed (Vasily Fedoseyev) 15 Feb '24

15 Feb '24

Issue #20268 has been reported by vasfed (Vasily Fedoseyev). ---------------------------------------- Bug #20268: Segfault in ruby 3.3 Fiber on aarch64 musl (mac m1) https://bugs.ruby-lang.org/issues/20268 * Author: vasfed (Vasily Fedoseyev) * Status: Open * Priority: Normal * ruby -v: 3.3.0 * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- On mac m1pro the following ```sh docker run --platform linux/aarch64 --rm -it ruby:3.3.0-alpine3.19 ruby -e 'Fiber.new { puts 123 }.resume' ``` produces segfault: ``` -e:1: [BUG] Segmentation fault at 0x006cffff93eecfd0 ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [aarch64-linux-musl] -- Control frame information ----------------------------------------------- c:0003 p:---- s:0010 e:000009 CFUNC :resume c:0002 p:0007 s:0006 E:000260 EVAL -e:1 [FINISH] c:0001 p:0000 s:0003 E:000b40 DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- -e:1:in `<main>' -e:1:in `resume' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 1 -- Machine register context ------------------------------------------------ x0: 0x0000ffff943ed9a0 x1: 0x0000ffff7911af30 x2: 0x0000ffffec47f610 x3: 0x0000ffff7a67df60 x4: 0x0000ffff7a67e018 x5: 0x0000ffff7a69e000 x6: 0x0000ffff944afff0 x7: 0x0000000000000000 x18: 0x0000ffff78ef0290 x19: 0x0000000000000000 x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000000 x23: 0x0000000000000000 x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000 x28: 0x0000000000000000 x29: 0x0000000000000000 sp: 0x0000ffff7a67e000 fau: 0x006cffff93eecfd0 -- Other runtime information ----------------------------------------------- * Loaded script: -e * Loaded features: 0 enumerator.so 1 thread.rb 2 fiber.so 3 rational.so 4 complex.so 5 ruby2_keywords.rb 6 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/encdb.so 7 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/trans/transdb.so 8 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/rbconfig.rb 9 /usr/local/lib/ruby/3.3.0/rubygems/compatibility.rb 10 /usr/local/lib/ruby/3.3.0/rubygems/defaults.rb 11 /usr/local/lib/ruby/3.3.0/rubygems/deprecate.rb 12 /usr/local/lib/ruby/3.3.0/rubygems/errors.rb 13 /usr/local/lib/ruby/3.3.0/rubygems/unknown_command_spell_checker.rb 14 /usr/local/lib/ruby/3.3.0/rubygems/exceptions.rb 15 /usr/local/lib/ruby/3.3.0/rubygems/basic_specification.rb 16 /usr/local/lib/ruby/3.3.0/rubygems/stub_specification.rb 17 /usr/local/lib/ruby/3.3.0/rubygems/platform.rb 18 /usr/local/lib/ruby/3.3.0/rubygems/util/list.rb 19 /usr/local/lib/ruby/3.3.0/rubygems/version.rb 20 /usr/local/lib/ruby/3.3.0/rubygems/requirement.rb 21 /usr/local/lib/ruby/3.3.0/rubygems/specification.rb 22 /usr/local/lib/ruby/3.3.0/rubygems/util.rb 23 /usr/local/lib/ruby/3.3.0/rubygems/dependency.rb 24 /usr/local/lib/ruby/3.3.0/rubygems/core_ext/kernel_gem.rb 25 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/monitor.so 26 /usr/local/lib/ruby/3.3.0/monitor.rb 27 /usr/local/lib/ruby/3.3.0/rubygems.rb 28 /usr/local/lib/ruby/3.3.0/bundled_gems.rb 29 /usr/local/lib/ruby/3.3.0/rubygems/path_support.rb 30 /usr/local/lib/ruby/3.3.0/error_highlight/version.rb 31 /usr/local/lib/ruby/3.3.0/error_highlight/base.rb 32 /usr/local/lib/ruby/3.3.0/error_highlight/formatter.rb 33 /usr/local/lib/ruby/3.3.0/error_highlight/core_ext.rb 34 /usr/local/lib/ruby/3.3.0/error_highlight.rb 35 /usr/local/lib/ruby/3.3.0/did_you_mean/version.rb 36 /usr/local/lib/ruby/3.3.0/did_you_mean/core_ext/name_error.rb 37 /usr/local/lib/ruby/3.3.0/did_you_mean/levenshtein.rb 38 /usr/local/lib/ruby/3.3.0/did_you_mean/jaro_winkler.rb 39 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checker.rb 40 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/name_error_checkers/class_name_checker.rb 41 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/name_error_checkers/variable_name_checker.rb 42 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/name_error_checkers.rb 43 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/method_name_checker.rb 44 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/key_error_checker.rb 45 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/null_checker.rb 46 /usr/local/lib/ruby/3.3.0/did_you_mean/tree_spell_checker.rb 47 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/require_path_checker.rb 48 /usr/local/lib/ruby/3.3.0/did_you_mean/spell_checkers/pattern_key_name_checker.rb 49 /usr/local/lib/ruby/3.3.0/did_you_mean/formatter.rb 50 /usr/local/lib/ruby/3.3.0/did_you_mean.rb 51 /usr/local/lib/ruby/3.3.0/syntax_suggest/core_ext.rb * Process memory map: aaaac56e0000-aaaac56e1000 r-xp 00000000 fe:01 3134602 /usr/local/bin/ruby aaaac56ff000-aaaac5700000 r--p 0000f000 fe:01 3134602 /usr/local/bin/ruby aaaac5700000-aaaac5701000 rw-p 00010000 fe:01 3134602 /usr/local/bin/ruby aaaacdc11000-aaaacdc12000 ---p 00000000 00:00 0 [heap] aaaacdc12000-aaaacdc1d000 rw-p 00000000 00:00 0 [heap] ffff78bcd000-ffff78bdd000 rw-p 00000000 00:00 0 ffff78e10000-ffff78e45000 rw-p 00000000 00:00 0 ffff78e51000-ffff78e82000 rw-p 00000000 00:00 0 ffff78e82000-ffff78ea1000 r-xp 00000000 fe:01 3134882 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/monitor.so ffff78ea1000-ffff78ea2000 r--p 0000f000 fe:01 3134882 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/monitor.so ffff78ea2000-ffff78ea3000 rw-p 00010000 fe:01 3134882 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/monitor.so ffff78ea3000-ffff78f00000 rw-p 00000000 00:00 0 ffff78f07000-ffff78f76000 rw-p 00000000 00:00 0 ffff78f77000-ffff78f7f000 rw-p 00000000 00:00 0 ffff78f8c000-ffff78fa8000 rw-p 00000000 00:00 0 ffff78faa000-ffff78fac000 rw-p 00000000 00:00 0 ffff78faf000-ffff78fc2000 rw-p 00000000 00:00 0 ffff78fc3000-ffff790c5000 rw-p 00000000 00:00 0 ffff790c9000-ffff79185000 rw-p 00000000 00:00 0 ffff79187000-ffff79189000 rw-p 00000000 00:00 0 ffff7918b000-ffff79191000 rw-p 00000000 00:00 0 ffff79198000-ffff791ff000 rw-p 00000000 00:00 0 ffff791ff000-ffff7921e000 r-xp 00000000 fe:01 3134859 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/trans/transdb.so ffff7921e000-ffff7921f000 r--p 0000f000 fe:01 3134859 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/trans/transdb.so ffff7921f000-ffff79220000 rw-p 00010000 fe:01 3134859 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/trans/transdb.so ffff79220000-ffff7923d000 rw-p 00000000 00:00 0 ffff7923d000-ffff7925c000 r-xp 00000000 fe:01 3134816 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/encdb.so ffff7925c000-ffff7925d000 r--p 0000f000 fe:01 3134816 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/encdb.so ffff7925d000-ffff7925e000 rw-p 00010000 fe:01 3134816 /usr/local/lib/ruby/3.3.0/aarch64-linux-musl/enc/encdb.so ffff7925e000-ffff7925f000 ---p 00000000 00:00 0 ffff7925f000-ffff79300000 rw-p 00000000 00:00 0 ffff79300000-ffff79301000 ---p 00000000 00:00 0 ffff79301000-ffff793a2000 rw-p 00000000 00:00 0 ffff793a2000-ffff793a3000 ---p 00000000 00:00 0 ffff793a3000-ffff79444000 rw-p 00000000 00:00 0 ffff79444000-ffff79445000 ---p 00000000 00:00 0 ffff79445000-ffff794e6000 rw-p 00000000 00:00 0 ffff794e6000-ffff794e7000 ---p 00000000 00:00 0 ffff794e7000-ffff79588000 rw-p 00000000 00:00 0 ffff79588000-ffff79589000 ---p 00000000 00:00 0 ffff79589000-ffff7962a000 rw-p 00000000 00:00 0 ffff7962a000-ffff7962b000 ---p 00000000 00:00 0 ffff7962b000-ffff796cc000 rw-p 00000000 00:00 0 ffff796cc000-ffff796cd000 ---p 00000000 00:00 0 ffff796cd000-ffff7976e000 rw-p 00000000 00:00 0 ffff7976e000-ffff7976f000 ---p 00000000 00:00 0 ffff7976f000-ffff79810000 rw-p 00000000 00:00 0 ffff79810000-ffff79811000 ---p 00000000 00:00 0 ffff79811000-ffff798b2000 rw-p 00000000 00:00 0 ffff798b2000-ffff798b3000 ---p 00000000 00:00 0 ffff798b3000-ffff79954000 rw-p 00000000 00:00 0 ffff79954000-ffff79955000 ---p 00000000 00:00 0 ffff79955000-ffff799f6000 rw-p 00000000 00:00 0 ffff799f6000-ffff799f7000 ---p 00000000 00:00 0 ffff799f7000-ffff79a98000 rw-p 00000000 00:00 0 ffff79a98000-ffff79a99000 ---p 00000000 00:00 0 ffff79a99000-ffff79b3a000 rw-p 00000000 00:00 0 ffff79b3a000-ffff79b3b000 ---p 00000000 00:00 0 ffff79b3b000-ffff79bdc000 rw-p 00000000 00:00 0 ffff79bdc000-ffff79bdd000 ---p 00000000 00:00 0 ffff79bdd000-ffff79c7e000 rw-p 00000000 00:00 0 ffff79c7e000-ffff79c7f000 ---p 00000000 00:00 0 ffff79c7f000-ffff79d20000 rw-p 00000000 00:00 0 ffff79d20000-ffff79d21000 ---p 00000000 00:00 0 ffff79d21000-ffff79dc2000 rw-p 00000000 00:00 0 ffff79dc2000-ffff79dc3000 ---p 00000000 00:00 0 ffff79dc3000-ffff79e64000 rw-p 00000000 00:00 0 ffff79e64000-ffff79e65000 ---p 00000000 00:00 0 ffff79e65000-ffff79f06000 rw-p 00000000 00:00 0 ffff79f06000-ffff79f07000 ---p 00000000 00:00 0 ffff79f07000-ffff79fa8000 rw-p 00000000 00:00 0 ffff79fa8000-ffff79fa9000 ---p 00000000 00:00 0 ffff79fa9000-ffff7a04a000 rw-p 00000000 00:00 0 ffff7a04a000-ffff7a04b000 ---p 00000000 00:00 0 ffff7a04b000-ffff7a0ec000 rw-p 00000000 00:00 0 ffff7a0ec000-ffff7a0ed000 ---p 00000000 00:00 0 ffff7a0ed000-ffff7a18e000 rw-p 00000000 00:00 0 ffff7a18e000-ffff7a18f000 ---p 00000000 00:00 0 ffff7a18f000-ffff7a230000 rw-p 00000000 00:00 0 ffff7a230000-ffff7a231000 ---p 00000000 00:00 0 ffff7a231000-ffff7a2d2000 rw-p 00000000 00:00 0 ffff7a2d2000-ffff7a2d3000 ---p 00000000 00:00 0 ffff7a2d3000-ffff7a374000 rw-p 00000000 00:00 0 ffff7a374000-ffff7a375000 ---p 00000000 00:00 0 ffff7a375000-ffff7a416000 rw-p 00000000 00:00 0 ffff7a416000-ffff7a417000 ---p 00000000 00:00 0 ffff7a417000-ffff7a4b8000 rw-p 00000000 00:00 0 ffff7a4b8000-ffff7a4b9000 ---p 00000000 00:00 0 ffff7a4b9000-ffff7a55a000 rw-p 00000000 00:00 0 ffff7a55a000-ffff7a55b000 ---p 00000000 00:00 0 ffff7a55b000-ffff7a5fc000 rw-p 00000000 00:00 0 ffff7a5fc000-ffff7a5fd000 ---p 00000000 00:00 0 ffff7a5fd000-ffff7a6b2000 rw-p 00000000 00:00 0 ffff7a6b2000-ffff7a6b4000 ---p 00000000 00:00 0 ffff7a6b4000-ffff93d27000 rw-p 00000000 00:00 0 ffff93d27000-ffff93d56000 r-xp 00000000 fe:01 3134315 /usr/lib/libgcc_s.so.1 ffff93d56000-ffff93d57000 r--p 0001f000 fe:01 3134315 /usr/lib/libgcc_s.so.1 ffff93d57000-ffff93d58000 rw-p 00020000 fe:01 3134315 /usr/lib/libgcc_s.so.1 ffff93d58000-ffff93dd6000 r-xp 00000000 fe:01 3134319 /usr/lib/libgmp.so.10.5.0 ffff93dd6000-ffff93dd8000 r--p 0006e000 fe:01 3134319 /usr/lib/libgmp.so.10.5.0 ffff93dd8000-ffff93dd9000 rw-p 00070000 fe:01 3134319 /usr/lib/libgmp.so.10.5.0 ffff93dd9000-ffff93e08000 r-xp 00000000 fe:01 49695 /lib/libz.so.1.3.1 ffff93e08000-ffff93e09000 r--p 0001f000 fe:01 49695 /lib/libz.so.1.3.1 ffff93e09000-ffff93e0a000 rw-p 00020000 fe:01 49695 /lib/libz.so.1.3.1 ffff93e0a000-ffff943c1000 r-xp 00000000 fe:01 3134798 /usr/local/lib/libruby.so.3.3.0 ffff943c1000-ffff943da000 r--p 005b7000 fe:01 3134798 /usr/local/lib/libruby.so.3.3.0 ffff943da000-ffff943db000 rw-p 005d0000 fe:01 3134798 /usr/local/lib/libruby.so.3.3.0 ffff943db000-ffff943ee000 rw-p 00000000 00:00 0 ffff943ee000-ffff94490000 r-xp 00000000 fe:01 49689 /lib/ld-musl-aarch64.so.1 ffff94490000-ffff944aa000 rw-p 00000000 00:00 0 ffff944aa000-ffff944ac000 r--p 00000000 00:00 0 [vvar] ffff944ac000-ffff944ad000 r-xp 00000000 00:00 0 [vdso] ffff944ad000-ffff944af000 rw-p 000af000 fe:01 49689 /lib/ld-musl-aarch64.so.1 ffff944af000-ffff944b1000 rw-p 00000000 00:00 0 ffffebc82000-ffffec481000 rw-p 00000000 00:00 0 [stack] ``` This only occurs for 3.3 on aarch64 platform (same for alpine3.18), `docker run --platform linux/amd64 --rm -it ruby:3.3.0-alpine3.19 ruby -e 'Fiber.new { puts 123 }.resume'` and aarch64 ruby:3.2.3-alpine3.19 on the same machine works correctly. -- https://bugs.ruby-lang.org/

2 1

[ruby-core:116220] [Ruby master Bug#20187] Bundled gems at Ruby 3.3
by hsbt (Hiroshi SHIBATA) 15 Feb '24

15 Feb '24

Issue #20187 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #20187: Bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/20187 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- This ticket is for tracking bundled gems status at Ruby 3.4. I added warnings for bundled gems of Ruby 3.3 at https://bugs.ruby-lang.org/issues/19351 and https://bugs.ruby-lang.org/issues/19776. I started to extract(promote) target libraries to bundled gems. These are: * abbrev * base64 * bigdecimal * csv * drb * getoptlong * mutex_m * nkf * observer * resolv-replace * rinda * syslog -- https://bugs.ruby-lang.org/

2 6

[ruby-core:116610] [Ruby master Misc#20242] `--parser=prism_without_warning`
by kddnewton (Kevin Newton) 14 Feb '24

14 Feb '24

Issue #20242 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Misc #20242: `--parser=prism_without_warning` https://bugs.ruby-lang.org/issues/20242 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- I was hoping to add another option to `--parser` which would be `--parser=prism_without_warning`. The issue is that it's making it hard to run the tests/specs that test against the output of stderr. This would do the exact same thing as `--parser=prism` it just wouldn't warn. (The name is derived from `--dump=insns_without_opt`, but I'm okay with anything. -- https://bugs.ruby-lang.org/

3 6

[ruby-core:116696] [Ruby master Bug#20264] Segfault installing RMagick on M1 Mac
by andy＠andyjeffries.co.uk (Andy Jeffries) 14 Feb '24

14 Feb '24

Issue #20264 has been reported by andy(a)andyjeffries.co.uk (Andy Jeffries). ---------------------------------------- Bug #20264: Segfault installing RMagick on M1 Mac https://bugs.ruby-lang.org/issues/20264 * Author: andy(a)andyjeffries.co.uk (Andy Jeffries) * Status: Open * Priority: Normal * ruby -v: 3.3 * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I raised a bug at RMagick, they said to go to pkg-config. I raised a bug there, and they said to raise it here. Hopefully this is the right place... https://github.com/ruby-gnome/pkg-config/issues/24 Simplest reproduction steps (although a full backtrace of a Rails app trying to do it is at the link above): ``` $ docker run -it --platform=linux/arm64 registry.docker.com/library/ruby:3.3-slim bash root@163711a82570:/# apt-get update root@163711a82570:/# apt-get install --no-install-recommends -y build-essential pkg-config libmagickwand-dev root@163711a82570:/# gem install rmagick ``` -- https://bugs.ruby-lang.org/

4 6

[ruby-core:116631] [Ruby master Bug#20247] net/http/header limits are too low
by dpsi (Darien Imai) 14 Feb '24

14 Feb '24

Issue #20247 has been reported by dpsi (Darien Imai). ---------------------------------------- Bug #20247: net/http/header limits are too low https://bugs.ruby-lang.org/issues/20247 * Author: dpsi (Darien Imai) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) +YJIT [x86_64-linux] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Hello, some of my HTTP tests are failing on Ruby 3.3 due to ArgumentError too long. I am trying to update from Ruby 2.7. I did not see any mention of this change in the net/http changelog, but looking at git history, the limit was added between gem versions 0.3.2 and 0.4.0. https://github.com/ruby/ruby/commit/d8b8294c28a09278de357c26b291abf1b9f3cc5d I send HTTP requests with long header keys in my testing suite. Many webservers such as apache, nginx, IIS permit the total length of HTTP headers to be 8K or longer. Tomcat for example allows 48K. I am trying to send a request with a header key length of 24K. I think the limit of 1K is too low. There was not a clear reason for the change, so I request that it gets reverted. Alternatively the limit could be configurable. The code being affected by the limit was written for Ruby 1.8, so I am surprised such longstanding behaviour was removed without being listed in the changelog. -- https://bugs.ruby-lang.org/

3 3

[ruby-core:116435] [Ruby master Misc#20210] Invalid source encoding raises ArgumentError, not SyntaxError
by kddnewton (Kevin Newton) 14 Feb '24

14 Feb '24

Issue #20210 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Misc #20210: Invalid source encoding raises ArgumentError, not SyntaxError https://bugs.ruby-lang.org/issues/20210 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- I was hoping we could change the error that is raised when an invalid source encoding is found from an ArgumentError to a SyntaxError. First let me say, if this isn't possible for backward compatibility, I understand. Please do not take this as me not caring about backward compatibility. Right now, if you have the script `# encoding: foo\n"bar"`, it will raise an ArgumentError, not a SyntaxError. If there are other syntax errors in the file, there's no way to concat them together to give feedback to the user. If a user wants to consistently handle the errors coming back from a parse, they currently have to rescue ArgumentError and SyntaxError. Ideally it would all be SyntaxError, so we could handle them consistently and append all errors together. -- https://bugs.ruby-lang.org/

6 7

[ruby-core:115991] [Ruby master Bug#20111] `defined?` returns `expression` for assignment operators combined with fully qualified constants
by andrykonchin (Andrew Konchin) 14 Feb '24

14 Feb '24

Issue #20111 has been reported by andrykonchin (Andrew Konchin). ---------------------------------------- Bug #20111: `defined?` returns `expression` for assignment operators combined with fully qualified constants https://bugs.ruby-lang.org/issues/20111 * Author: andrykonchin (Andrew Konchin) * Status: Open * Priority: Normal * ruby -v: 3.2.2 * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- `defined?` doesn't consider &&=, ||= and other ...= operators as `assignment`: ```ruby defined?(A::B += 1) # => "expression" defined?(A::B &&= true) # => "expression" defined?(A::B ||= true) # => "expression" ``` But consider as `assignment` ordinal assignment: ```ruby defined?(A::B = 1) # => "assignment" ``` Wondering if it's expected behaviour. -- https://bugs.ruby-lang.org/

4 4