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

[ruby-core:116044] [Ruby master Misc#20156] C99 updates
by kddnewton (Kevin Newton) 08 Jan '24

08 Jan '24

Issue #20156 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Misc #20156: C99 updates https://bugs.ruby-lang.org/issues/20156 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Now that we require Visual Studio 2015 and Oracle Developer Studio 12.5, we can do a couple of things to clean up: * We should be able to remove our custom `stdbool.h` (added in VS2015 and Oracle SS 12.3) * Remove our usage of `__restrict` for Windows (added in VS2015) * Remove our custom `va_copy` (added in VS2015) Just notating, a couple of things that we _can_ use now: * snprintf * size_t printf format specifier (%z) I'm happy to do this work, but I wanted to open this ticket in case there is something besides Visual Studio or Oracle Solaris Studio that I would have missed for one of our compilation targets. Are there any other targets that do not fully implement C99? -- https://bugs.ruby-lang.org/

2 2

[ruby-core:116060] [Ruby master Feature#18285] NoMethodError#message uses a lot of CPU/is really expensive to call
by headius (Charles Nutter) 06 Jan '24

06 Jan '24

Issue #18285 has been updated by headius (Charles Nutter). Also fixes my issue from 2014: https://bugs.ruby-lang.org/issues/9725 I'm glad we finally have dealt with this one. ---------------------------------------- Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call https://bugs.ruby-lang.org/issues/18285#change-106058 * Author: ivoanjo (Ivo Anjo) * Status: Closed * Priority: Normal ---------------------------------------- Hello there! I'm working at Datadog on the ddtrace gem -- https://github.com/DataDog/dd-trace-rb and we ran into this issue on one of our internal testing applications. I also blogged about this issue in <https://ivoanjo.me/blog/2021/11/01/nomethoderror-ruby-cost/>. ### Background While testing an application that threw a lot of `NoMethodError`s in a Rails controller (this was used for validation), we discovered that service performance was very much impacted when we were logging these exceptions. While investigating with a profiler, the performance impact was caused by calls to `NoMethodError#message`, because this Rails controller had a quite complex `#inspect` method, that was getting called every time we tried to get the `#message` from the exception. ### How to reproduce ```ruby require 'bundler/inline' gemfile do source 'https://rubygems.org' gem 'benchmark-ips' end puts RUBY_DESCRIPTION class GemInformation # ... def get_no_method_error method_does_not_exist rescue => e e end def get_runtime_error raise 'Another Error' rescue => e e end def inspect # <-- expensive method gets called when calling NoMethodError#message Gem::Specification._all.inspect end end NO_METHOD_ERROR_INSTANCE = GemInformation.new.get_no_method_error RUNTIME_ERROR_INSTANCE = GemInformation.new.get_runtime_error Benchmark.ips do |x| x.config(:time => 5, :warmup => 2) x.report("no method error message cost") { NO_METHOD_ERROR_INSTANCE.message } x.report("runtime error message cost") { RUNTIME_ERROR_INSTANCE.message } x.compare! end ``` ### Expectation and result Getting the `#message` from a `NoMethodError` should be no costly than getting it from any other exception. In reality: ``` ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux] no method error message cost 115.390 (± 1.7%) i/s - 580.000 in 5.027822s runtime error message cost 6.938M (± 0.5%) i/s - 35.334M in 5.092617s Comparison: runtime error message cost: 6938381.6 i/s no method error message cost: 115.4 i/s - 60130.02x (± 0.00) slower ``` ### Suggested solutions 1. Do not call `#inspect` on the object on which the method was not found (see <https://github.com/ruby/ruby/blob/e0915ba67964d843832148aeca29a1f8244ca7b1/…>) 2. Cache result of calling `#message` after the first call. Ideally this should be done together with suggestion 1. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116003] [Ruby master Bug#20146] Code using Ractor with env `RUBY_MAX_CPU=1` ends with unreachable
by shia (Sangyong Sim) 06 Jan '24

06 Jan '24

Issue #20146 has been reported by shia (Sangyong Sim). ---------------------------------------- Bug #20146: Code using Ractor with env `RUBY_MAX_CPU=1` ends with unreachable https://bugs.ruby-lang.org/issues/20146 * Author: shia (Sangyong Sim) * Status: Open * Priority: Normal * ruby -v: ruby 3.4.0dev * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- ## Reproducible code ```rb # sample-code.rb Ractor.new { 1 } ``` ```bash RUBY_MAX_CPU=1 ruby sample-code.rb # This will not end with exit code 0 RUBY_MAX_CPU=2 ruby sample-code.rb # This ends with exit code 0 as expected ``` ## Expected process with RUBY_MAX_CPU=1 exits successfully as same as RUBY_MAX_CPU more than 1. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:115984] [Ruby master Misc#20107] Update required Oracle Solaris Studio version to 12.5
by kddnewton (Kevin Newton) 05 Jan '24

05 Jan '24

Issue #20107 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Misc #20107: Update required Oracle Solaris Studio version to 12.5 https://bugs.ruby-lang.org/issues/20107 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Per https://www.oracle.com/us/assets/lifetime-support-hardware-301321.pdf and https://www.oracle.com/a/ocom/docs/support/advanced-customer-support/solari…, 12.2, 12.3, and 12.4 are all end-of-life for "extended support". We should drop these old compilers from our support suite for Ruby 3.4.0 so that we can use more of C99. Specifically, in conjunction with bumping to Visual Studio 2015, I believe this means we can now rely on `stdbool.h`, the `restrict` keyword, `va_copy`, `snprintf`, and the `%zu` printf specifier all functioning as expected. -- https://bugs.ruby-lang.org/

4 6

[ruby-core:116035] [Ruby master Feature#14602] Version of dig that raises error if a key is not present
by edmz (Ed Mz) 05 Jan '24

05 Jan '24

Issue #14602 has been updated by edmz (Ed Mz). Following what @mame explained about Matz expectations, I would like to (*humbly*) suggest another option: * `dig_expected` (and a my +1 to `dig_strict`) ---------------------------------------- Feature #14602: Version of dig that raises error if a key is not present https://bugs.ruby-lang.org/issues/14602#change-106033 * Author: amcaplan (Ariel Caplan) * Status: Open * Priority: Normal ---------------------------------------- Currently, if I have a hash like this: ~~~ ruby { :name => { :first => "Ariel", :last => "Caplan" } } ~~~ and I want to navigate confidently and raise a KeyError if something is missing, I can do: ~~~ ruby hash.fetch(:name).fetch(:first) ~~~ Unfortunately, the length of the name, combined with the need to repeat the method name every time, means most programmers are more likely to do this: ~~~ ruby hash[:name][:first] ~~~ which leads to many unexpected errors. The Hash#dig method made it easy to access methods safely from a nested hash; I'd like to have something similar for access without error protection, and I'd think the most natural name would be Hash#dig!. It would work like this: ~~~ ruby hash = { :name => { :first => "Ariel", :last => "Caplan" } } hash.dig!(:name, :first) # => Ariel hash.dig!(:name, :middle) # raises KeyError (key not found: :middle) hash.dig!(:name, :first, :foo) # raises TypeError (String does not have #dig! method) ~~~ -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116034] [Ruby master Feature#18035] Introduce general model/semantic for immutability.
by Dan0042 (Daniel DeLorme) 05 Jan '24

05 Jan '24

Issue #18035 has been updated by Dan0042 (Daniel DeLorme). I understand the advantages of immutability, but I worry about the overall direction this is taking us. So I'll just quote something @mame wrote previously, as it reflects my own opinion. mame (Yusuke Endoh) wrote in #16153#note-6: > I'm against making Ruby immutable by default. One of the most important properties of Ruby is dynamics. Ruby has allowed users to change almost anything in run time: dynamically (re)defining classes and methods (including core builtin ones), manipulating instance variables and local variables (via Binding) through encapsulation, etc. These features are not recommended to abuse, but they actually bring big flexibility: monkey-patching, DRY, flexible operation, etc. However, blindly freezing objects may spoil this usefulness. > > It is a bit arguable if this flexibility limits performance. Some people say that it is possible to make Ruby fast with the flexibility kept (TruffleRuby proves it). That being said, I admit that the flexibility actually limits performance in the current MRI, and that we have no development resource to improve MRI so much in near future. I think that my proposal #11934 was one possible way to balance the flexibility and performance. Anyway, we need to estimate how much Ruby can be faster if the flexibility is dropped. If it becomes 10 times faster, it is worth considering of course. If it becomes 10 percent faster, it does not pay (in my opinion). ---------------------------------------- Feature #18035: Introduce general model/semantic for immutability. https://bugs.ruby-lang.org/issues/18035#change-106031 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- It would be good to establish some rules around mutability, immutability, frozen, and deep frozen in Ruby. I see time and time again, incorrect assumptions about how this works in production code. Constants that aren't really constant, people using `#freeze` incorrectly, etc. I don't have any particular preference but: - We should establish consistent patterns where possible, e.g. - Objects created by `new` are mutable. - Objects created by literal are immutable. We have problems with how `freeze` works on composite data types, e.g. `Hash#freeze` does not impact children keys/values, same for Array. Do we need to introduce `freeze(true)` or `#deep_freeze` or some other method? Because of this, frozen does not necessarily correspond to immutable. This is an issue which causes real world problems. I also propose to codify this where possible, in terms of "this class of object is immutable" should be enforced by the language/runtime, e.g. ```ruby module Immutable def new(...) super.freeze end end class MyImmutableObject extend Immutable def initialize(x) @x = x end def freeze return self if frozen? @x.freeze super end end o = MyImmutableObject.new([1, 2, 3]) puts o.frozen? ``` Finally, this area has an impact to thread and fiber safe programming, so it is becoming more relevant and I believe that the current approach which is rather adhoc is insufficient. I know that it's non-trivial to retrofit existing code, but maybe it can be done via magic comment, etc, which we already did for frozen string literals. Proposed PR: https://github.com/ruby/ruby/pull/4879 -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116013] [Ruby master Bug#20148] Sorting not working as expected on Urdu words.
by zohaibnadeem13＠gmail.com (Zohaib Nadeem) 05 Jan '24

05 Jan '24

Issue #20148 has been reported by zohaibnadeem13(a)gmail.com (Zohaib Nadeem). ---------------------------------------- Bug #20148: Sorting not working as expected on Urdu words. https://bugs.ruby-lang.org/issues/20148 * Author: zohaibnadeem13(a)gmail.com (Zohaib Nadeem) * Status: Open * Priority: Normal * ruby -v: 3.1.4 * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I was trying to sort an array of Urdu characters and found out an ambiguity in the result. Here is the script that I am using. ['ا', 'پ', 'ب', 'ت', 'ٹ'].sort Actual Result: ["ا", "ب", "ت", "ٹ", "پ"] Expected Result: ["ا", "ب", 'پ', "ت", "ٹ"] -- https://bugs.ruby-lang.org/

4 3

[ruby-core:115982] [Ruby master Bug#20106] Backport d3933fc753187a055a4904af82f5f3794c88c416 to fix net-http test errors
by vo.x (Vit Ondruch) 05 Jan '24

05 Jan '24

Issue #20106 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #20106: Backport d3933fc753187a055a4904af82f5f3794c88c416 to fix net-http test errors https://bugs.ruby-lang.org/issues/20106 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Testing with Ruby 3.3, I observe test errors such as: ~~~ 108) Failure: TestNetHTTPS#test_skip_hostname_verification [/builddir/build/BUILD/ruby-3.3.0/test/net/http/test_https.rb:217]: Exception raised: <#<OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 peeraddr=[::1]:45081 state=error: certificate verify failed (certificate has expired)>> Backtrace: /builddir/build/BUILD/ruby-3.3.0/lib/net/protocol.rb:46:in `connect_nonblock' /builddir/build/BUILD/ruby-3.3.0/lib/net/protocol.rb:46:in `ssl_socket_connect' /builddir/build/BUILD/ruby-3.3.0/lib/net/http.rb:1674:in `connect' /builddir/build/BUILD/ruby-3.3.0/lib/net/http.rb:1580:in `do_start' /builddir/build/BUILD/ruby-3.3.0/lib/net/http.rb:1575:in `start' /builddir/build/BUILD/ruby-3.3.0/test/net/http/test_https.rb:217:in `block (2 levels) in test_skip_hostname_verification'. ~~~ This is likely fixed by commit:git|d3933fc753187a055a4904af82f5f3794c88c416 -- https://bugs.ruby-lang.org/

2 1

[ruby-core:116023] [Ruby master Feature#13383] [PATCH] Module#source_location
by ioquatix (Samuel Williams) 04 Jan '24

04 Jan '24

Issue #13383 has been updated by ioquatix (Samuel Williams). If we decided to introduce this feature, I'm against using a plain Array. Let's use a well defined interface. ---------------------------------------- Feature #13383: [PATCH] Module#source_location https://bugs.ruby-lang.org/issues/13383#change-106016 * Author: koba789 (Hidekazu Kobayashi) * Status: Rejected * Priority: Normal * Assignee: ioquatix (Samuel Williams) ---------------------------------------- # Abstract It can inspect where the module or class is defined. # Background In debugging or development an application, I usually want to find out where the class definition of using library. There is Method#source_location but I could not find **Class** easily. # Implementation In Github: https://github.com/ruby/ruby/pull/1562 -- https://bugs.ruby-lang.org/

1 0

[ruby-core:112208] [Ruby master Bug#19409] Object's shape is reset after a ractor move
by luke-gru (Luke Gruber) 04 Jan '24

04 Jan '24

Issue #19409 has been reported by luke-gru (Luke Gruber). ---------------------------------------- Bug #19409: Object's shape is reset after a ractor move https://bugs.ruby-lang.org/issues/19409 * Author: luke-gru (Luke Gruber) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I believe an object should have the same shape after being moved from 1 ractor to another. ```ruby class Obj attr_accessor :a, :b, :c, :d def initialize @a = 1 @b = 2 @c = 3 end end r = Ractor.new do obj = receive #p RubyVM::Shape.of(obj) obj.d = 4 p obj.a, obj.b, obj.c, obj.d # gets wrong values due to object shape id being reset on object end obj = Obj.new #p RubyVM::Shape.of(obj) r.send(obj, move: true) r.take ``` -- https://bugs.ruby-lang.org/

2 2