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

[ruby-core:111896] [Ruby master Bug#18658] Need openssl 3 support for Ubuntu 22.04 (Ruby 2.7.x and 3.0.x)
by hsbt (Hiroshi SHIBATA) 19 Jan '23

19 Jan '23

Issue #18658 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Assigned Assignee changed from rhenium (Kazuki Yamaguchi) to hsbt (Hiroshi SHIBATA) I discussed @usa. * We want to backport [openssl-3.0.2 gem](https://github.com/ruby/openssl/releases/tag/v3.0.2) into `ruby_3_0` branch. * We need keep compatibility with OpenSSL-1.1 with openssl-3.0.2 gem I'll create a backport patch for `ruby_3_0` branch before moving `ruby_3_0` to security only status. ---------------------------------------- Bug #18658: Need openssl 3 support for Ubuntu 22.04 (Ruby 2.7.x and 3.0.x) https://bugs.ruby-lang.org/issues/18658#change-101314 * Author: schneems (Richard Schneeman) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: 3.0 * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Ubuntu 22.04 is being released soon and ships with openssl 3. As of now Ruby 2.7.x and 3.0.x are under core support and will not build on Ubuntu 22.04 with openssl (Ruby 3.1.x can compile). When attempting to compile 3.0.3 on Ubuntu 22 it issues this warning: ``` *** Following extensions are not compiled: openssl: Could not be configured. It will not be installed. /ruby-3.0.3/ext/openssl/extconf.rb:113: OpenSSL >= 1.0.1, < 3.0.0 or LibreSSL >= 2.5.0 is required Check ext/openssl/mkmf.log for more details. ``` Here are some existing issues/PRs that I could find: - https://github.com/ruby/openssl/issues/369 - https://github.com/ruby/openssl/pull/399 Ideally I would like to compile and support all non-EOL Ruby versions for Ubuntu 22 on release day. Are there any plans to backport support for OpenSSL 3 to Ruby 3.0 and 2.7? -- https://bugs.ruby-lang.org/

1 0

[ruby-core:111435] [Ruby master Bug#19262] Segmentation fault on RubyVM::AbstractSyntaxTree.node_id_for_backtrace_location
by ksss (Yuki Kurihara) 19 Jan '23

19 Jan '23

Issue #19262 has been reported by ksss (Yuki Kurihara). ---------------------------------------- Bug #19262: Segmentation fault on RubyVM::AbstractSyntaxTree.node_id_for_backtrace_location https://bugs.ruby-lang.org/issues/19262 * Author: ksss (Yuki Kurihara) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin21] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- It seems that `RubyVM::AbstractSyntaxTree.node_id_for_backtrace_location` gives a Segmentation fault if any argument other than `Thread::Backtrace::Location` is given. repro: ``` $ ruby -e 'RubyVM::AbstractSyntaxTree.node_id_for_backtrace_location(1)' ``` -- https://bugs.ruby-lang.org/

2 1

[ruby-core:111361] [Ruby master Bug#19248] TestGCCompact#test_moving_objects_between_size_pools test failure
by vo.x (Vit Ondruch) 19 Jan '23

19 Jan '23

Issue #19248 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #19248: TestGCCompact#test_moving_objects_between_size_pools test failure https://bugs.ruby-lang.org/issues/19248 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0dev (2022-12-21 master 6af6857ecf) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Testing on Fedora Rawhide with commit:git|6af6857ecf, I observe the following error: ~~~ 1) Error: TestGCCompact#test_moving_objects_between_size_pools: NoMethodError: undefined method `>=' for nil:NilClass /builddir/build/BUILD/ruby-3.2.0-6af6857ecf/test/ruby/test_gc_compact.rb:278:in `<main>' /builddir/build/BUILD/ruby-3.2.0-6af6857ecf/test/ruby/test_gc_compact.rb:256:in `test_moving_objects_between_size_pools' /builddir/build/BUILD/ruby-3.2.0-6af6857ecf/tool/test/runner.rb:23:in `<top (required)>' /builddir/build/BUILD/ruby-3.2.0-6af6857ecf/test/runner.rb:16:in `require_relative' /builddir/build/BUILD/ruby-3.2.0-6af6857ecf/test/runner.rb:16:in `<main>' ~~~ Testing previously with commit:git|11acb7f7bc, everything was fine. I might just guess that this is related to commit:git|bfc66e07b7e0134dfa2041c311dc56941fe1caf0 -- https://bugs.ruby-lang.org/

6 24

[ruby-core:111456] [Ruby master Bug#19271] irb ignores rbs and debug with YJIT enabled
by olivierlacan (Olivier Lacan) 18 Jan '23

18 Jan '23

Issue #19271 has been reported by olivierlacan (Olivier Lacan). ---------------------------------------- Bug #19271: irb ignores rbs and debug with YJIT enabled https://bugs.ruby-lang.org/issues/19271 * Author: olivierlacan (Olivier Lacan) * Status: Open * Priority: Normal * ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Not sure this is a serious issue but when starting IRB with YJIT enabled this (potentially confusing) message is immediately printed: ``` $ RUBY_YJIT_ENABLE=1 irb Ignoring debug-1.7.1 because its extensions are not built. Try: gem pristine debug --version 1.7.1 Ignoring rbs-2.8.2 because its extensions are not built. Try: gem pristine rbs --version 2.8.2 irb(main):001:0> ``` This is on a fresh installation of Ruby 3.2.0 with an empty Gemfile in the directory. I haven't run gem pristine on any gem since I hadn't installed any gems after installing Ruby 3.2.0 here but FYI: ``` $ gem list | grep "rbs\|debug" debug (1.7.1) rbs (2.8.2) ``` This seems to suggest that C extensions weren't built for those gems when they were installed during the Ruby installation process. Just to be safe I checked and while I do use rbenv and ruby-build to compile and manage Rubies, I don't have a default gem installer set up so as far as I know these gems weren't installed by my system. -- https://bugs.ruby-lang.org/

6 8

[ruby-core:111573] [Ruby master Bug#19298] `lib/mjit/instruction.rb` was reintroduced by merge mistake
by vo.x (Vit Ondruch) 18 Jan '23

18 Jan '23

Issue #19298 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #19298: `lib/mjit/instruction.rb` was reintroduced by merge mistake https://bugs.ruby-lang.org/issues/19298 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [x86_64-linux] * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: REQUIRED ---------------------------------------- It seems that `lib/mjit/instruction.rb` should not be shipped anymore since commit:git|bb4cbd0803c3297ad036008adc7a01159ce44e1e, but it was re-introduced into the repository by merge mistake commit:git|f6620037ba1477d2c337d7b511f094d6d0fbb69c. Actually, it was probably never part of the repository, but was part of the tarball, but it seems it should not be. -- https://bugs.ruby-lang.org/

4 3

[ruby-core:111800] [Ruby master Bug#19336] Backport commit eab7f4623fbf0488e828b75843d70c8e02dc8aa5
by byroot (Jean Boussier) 18 Jan '23

18 Jan '23

Issue #19336 has been reported by byroot (Jean Boussier). ---------------------------------------- Bug #19336: Backport commit eab7f4623fbf0488e828b75843d70c8e02dc8aa5 https://bugs.ruby-lang.org/issues/19336 * Author: byroot (Jean Boussier) * Status: Closed * Priority: Normal * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED, 3.2: REQUIRED ---------------------------------------- This commit fix a potential VM crash when profiling. -- https://bugs.ruby-lang.org/

2 1

[ruby-core:111571] [Ruby master Bug#19296] Time.new's argument check is incomplete
by matsuda (Akira Matsuda) 18 Jan '23

18 Jan '23

Issue #19296 has been reported by matsuda (Akira Matsuda). ---------------------------------------- Bug #19296: Time.new's argument check is incomplete https://bugs.ruby-lang.org/issues/19296 * Author: matsuda (Akira Matsuda) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0dev (2023-01-01T07:39:00Z master 542e984d82) +YJIT [arm64-darwin21] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- `Time.new` seems to be performing some sort of argument checking, but I found some strings that can bypass this validation and craft erroneous Time value. - month ``` '12'.upto('20').each do |m| str = "2023-#{m}-01" puts str begin p Time.new str rescue => e p e end puts end ``` ``` # result 2023-12-01 2023-12-01 00:00:00 +0900 2023-13-01 #<ArgumentError: mon out of range> 2023-14-01 #<ArgumentError: mon out of range> 2023-15-01 #<ArgumentError: mon out of range> 2023-16-01 #<ArgumentError: mon out of range> 2023-17-01 2023-01-01 00:00:00 +0900 2023-18-01 2023-02-01 00:00:00 +0900 2023-19-01 2023-03-01 00:00:00 +0900 2023-20-01 2023-04-01 00:00:00 +0900 ``` - day ``` $ ruby -e 'p Time.new("2023-01-31")' 2023-01-31 00:00:00 +0900 $ ruby -e 'p Time.new("2023-01-32")' <internal:timev>:398:in `initialize': mday out of range (ArgumentError) from -e:1:in `new' from -e:1:in `<main>' $ ruby -e 'p Time.new("2023-01-33")' 2023-01-01 00:00:00 +0900 $ ruby -e 'p Time.new("2023-01-34") 2023-01-02 00:00:00 +0900 ``` In conclusion, month seeems to raise only when the given value is <= 16, and day seems to be checked for <= 32 only. -- https://bugs.ruby-lang.org/

3 2

[ruby-core:111441] [Ruby master Bug#19264] Backport 9f2378959e5c5b5c39c9993f1a84e5304ff113d6
by nagachika (Tomoyuki Chikanaga) 18 Jan '23

18 Jan '23

Issue #19264 has been reported by nagachika (Tomoyuki Chikanaga). ---------------------------------------- Bug #19264: Backport 9f2378959e5c5b5c39c9993f1a84e5304ff113d6 https://bugs.ruby-lang.org/issues/19264 * Author: nagachika (Tomoyuki Chikanaga) * Status: Closed * Priority: Normal * Backport: 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED ---------------------------------------- This is a ticket for backport management. 9f2378959e5c5b5c39c9993f1a84e5304ff113d6 may need to be backported. https://github.com/ruby/ruby/pull/7023 -- https://bugs.ruby-lang.org/

2 1

[ruby-core:111857] [Ruby master Bug#19349] Kernel.Integer silently discards base argument that does not have a #to_int
by herwin (Herwin W) 18 Jan '23

18 Jan '23

Issue #19349 has been reported by herwin (Herwin W). ---------------------------------------- Bug #19349: Kernel.Integer silently discards base argument that does not have a #to_int https://bugs.ruby-lang.org/issues/19349 * Author: herwin (Herwin W) * Status: Open * Priority: Normal * ruby -v: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- The method `Kernel.Integer` has an optional argument `base`, which is the base to convert the input to: ``` irb(main):001:0> Kernel.Integer('10', 8) => 8 ``` If the base argument is not an integer, it is converted using `#to_int` ``` irb(main):002:0> Kernel.Integer('10', 8.2) => 8 irb(main):003:0> Kernel.Integer('10', Object.new.tap { |x| x.define_singleton_method(:to_int) { 8 } }) => 8 ``` But if the base argument is not an Integer, and does not have a `#to_int` method, it gets discarded ``` irb(main):004:0> Kernel.Integer('10', '8') => 10 ``` I would expect this to raise a `TypeError`, similar to `String#to_i`: ``` irb(main):005:0> '10'.to_i('8') (irb):5:in `to_i': no implicit conversion of String into Integer (TypeError) ``` This has briefly been discussed on the ruby-spec github repo, and they suggested to report this as a bug. (see https://github.com/ruby/spec/pull/997#issuecomment-1382825900) -- https://bugs.ruby-lang.org/

2 2

[ruby-core:111864] [Ruby master Bug#11230] Should rb_struct_s_members() be public API?
by jeremyevans0 (Jeremy Evans) 17 Jan '23

17 Jan '23

Issue #11230 has been updated by jeremyevans0 (Jeremy Evans). I submitted a pull request to remove the prototype from the public header files: https://github.com/ruby/ruby/pull/7141 `rb_struct_s_members` is still an exported symbol as it is used internally by `marshal.c`. One of reasons stated to remove this method is that it returns a hidden Array. However, `rb_struct_members` appears to return the same hidden Array (that method is also used internally by `marshal.c`). Should we consider removing `rb_struct_members` from the public API as well? ---------------------------------------- Bug #11230: Should rb_struct_s_members() be public API? https://bugs.ruby-lang.org/issues/11230#change-101278 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- rb_struct_s_members() is declared in include/ruby/intern.h. However it seems this is a fairly internal API as it returns an hidden Array. For instance, there was a try to specify the behavior in https://github.com/rubinius/rubinius/commit/2642a30c57973987d2a7b7e85b3ce1e… but that produces only erratic behavior on MRI because that usage is not intended. A valid usage might be: static VALUE get_struct_member(VALUE self, VALUE obj, VALUE i) { return RARRAY_AREF(rb_struct_s_members(obj), NUM2INT(i)); } p get_struct_member(Struct.new(:a, :bb), 1) But do we need such access and is it worth exposing a potentially dangerous function like this? -- https://bugs.ruby-lang.org/

1 0