January 2023 - ruby-core - ml.ruby-lang.org

[ruby-core:111624] [Ruby master Bug#19115] RubyGems fails to detect OpenSSL in --with-static-linked-ext builds
by thomthom (Thomas Thomassen) 04 Jan '23

04 Jan '23

Issue #19115 has been updated by thomthom (Thomas Thomassen). I built Ruby 3.1.2 that we use in our product with this patch applied, and it worked on our systems. Would be nice to see it backported. ---------------------------------------- Bug #19115: RubyGems fails to detect OpenSSL in --with-static-linked-ext builds https://bugs.ruby-lang.org/issues/19115#change-100995 * Author: thomthom (Thomas Thomassen) * Status: Closed * Priority: Normal * ruby -v: 3.1.2, 3.2.0dev * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Related discussion: https://bugs.ruby-lang.org/issues/18876 We are seeing OpenSSL failing to autoload with the Ruby build we've been using. (We first observed this when using `Gem.install` that relies on autoload of OpenSSL). Our last working build was Ruby 2.7.2 with similar config. This causes RubyGems' `HAVE_OPENSSL` constant to be incorrectly initialized, and subsequent calls to `Gem.install` fails. There might be other scenarios that fail as a result of that, but we've not managed to identified that. ``` module Gem HAVE_OPENSSL = defined? OpenSSL::SSL # :nodoc: ``` Our Ruby 3.1.2 config: ``` '--prefix=/Users/user/.conan/data/ruby/3.1.2/sketchup/stable/build/bd95825b99dcb274d0e577fbdc953653a9ea0fb9' '--with-openssl-dir=/Users/user/.conan/data/openssl/1.1.1q/sketchup/stable/package/93ae0b0e7eebe0611c04d3e0d9bbf49fbce92332' '--with-libyaml-dir=/Users/user/.conan/data/libyaml/0.2.5/sketchup/stable/package/a56a950abed2e10dbdc26845400f0a034d97c454' '--disable-install-doc' '--disable-install-rdoc' '--enable-shared' '--enable-load-relative' '--with-static-linked-ext' '--without-debug' '--without-gdbm' '--without-gettext' '--without-irb' '--without-mkmf' '--without-rdoc' '--without-readline' '--without-tk' '--bindir=${prefix}/bin' '--sbindir=${prefix}/bin' '--libexecdir=${prefix}/bin' '--libdir=${prefix}/lib' '--includedir=${prefix}/include' '--oldincludedir=${prefix}/include' '--datarootdir=${prefix}/share' 'cflags=-mmacosx-version-min=10.14 -fdeclspec' 'cxxflags=-mmacosx-version-min=10.14 -fdeclspec' 'LDFLAGS=-mmacosx-version-min=10.14 -fdeclspec' ``` We also tested with latest build from master (November 8th 2022): ``` ./ruby -ve 'p RbConfig::CONFIG["configure_args"]' ruby 3.2.0dev (2022-11-07T19:35:21Z master b14f133054) [x86_64-darwin20] " '--prefix=/Users/vmehta/ruby/ruby-master/' '--with-openssl-dir=/Users/vmehta/.conan/data/openssl/1.1.1q/sketchup/stable/package/f2d937af1fa19d5fc4095849a65d1927e9e75ae7/' '--with-libyaml-dir=/Users/vmehta/.conan/data/libyaml/0.2.5/sketchup/stable/package/3fc084e254210603a5c5aece184b2d45e2509b30' '--disable-install-doc' '--disable-install-rdoc' '--enable-shared' '--enable-load-relative' '--with-static-linked-ext' '--without-debug' '--without-gdbm' '--without-gettext' '--without-irb' '--without-mkmf' '--without-rdoc' '--without-readline' '--without-tk'" ``` Using an RVM of Ruby 3.1.2 this appear to work as expected. But using out configuration, that we've used for the Ruby 2.x versions are now failing. We haven't been able to figure out the reason for this. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:111453] [Ruby master Bug#19270] Constants lookup and a singleton class issue
by andrykonchin (Andrew Konchin) 04 Jan '23

04 Jan '23

Issue #19270 has been reported by andrykonchin (Andrew Konchin). ---------------------------------------- Bug #19270: Constants lookup and a singleton class issue https://bugs.ruby-lang.org/issues/19270 * Author: andrykonchin (Andrew Konchin) * Status: Open * Priority: Normal * ruby -v: 3.1.3 * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I've noticed that a constant declared in a singleton class may be not visible on an object: ```ruby class A def c; C; end end a = A.new klass = (class << a; self; end) klass.const_set(:C, 1) a.c # (irb):2:in `c': uninitialized constant A::C (NameError) ``` I would expect that such constant is visible and accessible on an object. It is expected and intentional behaviour? -- https://bugs.ruby-lang.org/

3 2

[ruby-core:111334] [Ruby master Bug#19244] Windows: USERPROFILE should be preferred over HOMEPATH
by larskanis (Lars Kanis) 03 Jan '23

03 Jan '23

Issue #19244 has been reported by larskanis (Lars Kanis). ---------------------------------------- Bug #19244: Windows: USERPROFILE should be preferred over HOMEPATH https://bugs.ruby-lang.org/issues/19244 * Author: larskanis (Lars Kanis) * Status: Open * Priority: Normal * ruby -v: ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x64-mingw-ucrt] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- Create a new local user on Windows called "testuser". Then switch to the new user per runas: ``` C:\> runas /user:testuser cmd ``` Then in the new window: ``` C:\>ruby -e "p Dir.home" "C:/WINDOWS/system32" C:\>echo %HOMEDRIVE% C: C:\>echo %HOMEPATH% \WINDOWS\system32 C:\>echo %USERPROFILE% C:\Users\testuser ``` `Dir.home` should return the home directory of the user. Instead it returns `C:/WINDOWS/system32`. HOMEPATH is set to "\WINDOWS\system32" when running per "runas" session. This directory is not writable by ordinary users, leading to errors with many ruby tools. Also config files in the home directory are not recognized. All versions of ruby until current master branch are affected. -- https://bugs.ruby-lang.org/

1 2

[ruby-core:111570] [Ruby master Bug#19295] Time#wday returns 7
by akostadinov (Aleksandar Kostadinov) 03 Jan '23

03 Jan '23

Issue #19295 has been reported by akostadinov (Aleksandar Kostadinov). ---------------------------------------- Bug #19295: Time#wday returns 7 https://bugs.ruby-lang.org/issues/19295 * Author: akostadinov (Aleksandar Kostadinov) * Status: Open * Priority: Normal * ruby -v: ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- This issue happens since Ruby 2.7, since `Z` and `UTC` are allowed for a zone. ``` ruby [1] pry(main)> Time.new(2023, 1,3,0,0,0,"UTC").wday => 7 [2] pry(main)> Time.new(2023, 1,3,0,0,0,"Z").wday => 7 ``` This also breaks all weekday `Time#monday?`, etc. methods. -- https://bugs.ruby-lang.org/

2 3

[ruby-core:111591] [Ruby master Feature#19303] Resolv::IPv4::Regex variant without anchors
by henk 03 Jan '23

03 Jan '23

Issue #19303 has been reported by henk (Hendrik Jäger). ---------------------------------------- Feature #19303: Resolv::IPv4::Regex variant without anchors https://bugs.ruby-lang.org/issues/19303 * Author: henk (Hendrik Jäger) * Status: Open * Priority: Normal ---------------------------------------- ``` ruby require 'resolv' p "match this IP: 10.0.0.1"[/match this IP: (#{Resolv::IPv4::Regex})/, 1] ``` This returns 'nil' because Resolv::IPv4::Regex is anchored with \A and \z. I would like to have a variant of Resolv::IPv4::Regex available that is not anchored so that code would return '10.0.0.1'. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:111586] [Ruby master Feature#14919] Add String#byteinsert
by noraj (Alexandre ZANNI) 02 Jan '23

02 Jan '23

Issue #14919 has been updated by noraj (Alexandre ZANNI). Yes a grapheme can be composed of several code points. An example is variant selector: ```ruby irb(main):001:0> a = "\u2665\n\u2764\n\u2665\ufe0f\n\u2764\ufe0f" => "♥\n❤\n♥️\n❤️" irb(main):002:0> puts a ♥ ❤ ♥️ ❤️ => nil irb(main):003:0> a.chars => ["♥", "\n", "❤", "\n", "♥", "️", "\n", "❤", "️"] ``` But fortunately, in Ruby, string indices are already mapping characters and not graphemes. So has Martin highlighted, `String#[]=` already cover all use cases I can think of. ```ruby irb(main):007:0> r = "I \u2665 Ruby!" => "I ♥ Ruby!" irb(main):009:0> r[2] = "\u2764\ufe0f" => "❤️" irb(main):010:0> r => "I ❤️ Ruby!" ``` The only thing I could think of `String#byteinsert` would be to directly mess with UTF-8 encoding to forge invalid encoding on purpose. But such a use case is rare and advanced and so can maybe be handled with pack and unpack rather than creating a new byteinsert method? ``` irb(main):014:0> r.unpack1('a*') => "I \xE2\x9D\xA4\xEF\xB8\x8F Ruby!" ``` @aycabta Maybe you could give me a handy example of the usage of `String#byteinsert` I can't think of? ---------------------------------------- Feature #14919: Add String#byteinsert https://bugs.ruby-lang.org/issues/14919#change-100956 * Author: aycabta (aycabta .) * Status: Open * Priority: Normal ---------------------------------------- It's important for multibyte String editing. Unicode grapheme characters sometimes have plural code points. In text editing, software sometimes should add a new code point to an existing grapheme character. String#byteinsert is important for it. I implemented by pure Ruby in my code. https://github.com/aycabta/reline/blob/b17e5fd61092adfd7e87d576301e4e19a4d9… -- https://bugs.ruby-lang.org/

1 0

[ruby-core:111556] [Ruby master Bug#19291] Ripper's on_parse_error token has wrong content
by tompng (tomoya ishida) 02 Jan '23

02 Jan '23

Issue #19291 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #19291: Ripper's on_parse_error token has wrong content https://bugs.ruby-lang.org/issues/19291 * Author: tompng (tomoya ishida) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [x86_64-darwin20] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Ruby 3.1 ~~~ruby Ripper::Lexer.new("{a:,aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\nhelloworld").scan.map(&:tok) # => ["{", "a:", ",", "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "", "\n", "helloworld"] ~~~ Ruby 3.2.0 ~~~ruby Ripper::Lexer.new("{a:,aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\nhelloworld").scan.map(&:tok) # => ["{", "a:", ",", "oworld\u0000\u0000\u0000\u0000\u0000\u0000z`\u0001\u0000\u0000\u0000\u0000\u0000\xC0\xF0$\u0010\u0001\u0000\u0000\u0000\x80A\xB8\u0019\xB5\u007F\u0000\u0000\x91\x94", "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "\n", "helloworld"] ~~~ -- https://bugs.ruby-lang.org/

2 1

[ruby-core:111563] [Ruby master Feature#16991] Sets: add Set#join
by zverok (Victor Shepelev) 01 Jan '23

01 Jan '23

Issue #16991 has been updated by zverok (Victor Shepelev). Status changed from Open to Closed Implemented in Ruby 3.0 ---------------------------------------- Feature #16991: Sets: add Set#join https://bugs.ruby-lang.org/issues/16991#change-100928 * Author: marcandre (Marc-Andre Lafortune) * Status: Closed * Priority: Normal ---------------------------------------- I'd like to add `#join` to `Set`: ```ruby # Now: Set[1, 2, 3].join('x') # => NoMethodError # After Set[1, 2, 3].join('x') # => "1x2x3" ``` I'd make this join never recursive. (I've never wanted to use the recursivity of `Array#join`, but it may very well just be my particular experience) Reminder: Why there is no `Enumerable#join`: https://bugs.ruby-lang.org/issues/1893 -- https://bugs.ruby-lang.org/

1 0

[ruby-core:111562] [Ruby master Feature#16995] Sets: <=> should be specialized
by zverok (Victor Shepelev) 01 Jan '23

01 Jan '23

Issue #16995 has been updated by zverok (Victor Shepelev). Status changed from Open to Closed Implemented in Ruby 3.0: ```ruby Set[1] <=> Set[1, 2] # => -1 [Set[1], Set[1, 2]].sort # => [#<Set: {1}>, #<Set: {1, 2}>] ``` ---------------------------------------- Feature #16995: Sets: <=> should be specialized https://bugs.ruby-lang.org/issues/16995#change-100927 * Author: marcandre (Marc-Andre Lafortune) * Status: Closed * Priority: Normal ---------------------------------------- This is quite minor, but `Set#<=>` should be refined. Reminder: `Set` defines `<`, `>`, etc. as inclusion, but does not have a corresponding `<=>`: ```ruby Set[1] < Set[1, 2] # => true Set[1] <=> Set[1, 2] # => nil, should be -1 Set[1] <=> Set[2] # => nil, ok, not orderable ``` The official stated reason for `Set` to *not* implement is that some sets are not comparable. That is exactly what `nil` result type is for IMO. Sets are partically ordered and `<=>` should reflect that. https://en.wikipedia.org/wiki/Partially_ordered_set ```ruby Set[1] < Set[1, 2] # => true [Set[1], Set[1, 2]].sort # => ArgumentError, should be [Set[1], Set[1, 2]] [Set[1], Set[2]].sort # => ArgumentError, ok, can't be ordered ``` This is *exactly the same* idea as `Class`, which correctly refines `<=>`: ```ruby Array < Enumerable # => true Array <=> Enumerable # => -1, ok [Array, Enumerable].sort # => [Array, Enumerable] [Array, String].sort # => ArgumentError (comparison of Class with Class failed), ok ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:111561] [Ruby master Feature#3591] Adding Numeric#divisor? (Have working implementation)
by e8c (Viktor Reznov) 01 Jan '23

01 Jan '23

Issue #3591 has been updated by e8c (Viktor Reznov). e8c (Viktor Reznov) wrote in #note-20: > Two solutions: 3rd: ```ruby def count_digits(n) = n.digits.count { n.modulo(_1).zero? } ``` ---------------------------------------- Feature #3591: Adding Numeric#divisor? (Have working implementation) https://bugs.ruby-lang.org/issues/3591#change-100926 * Author: duckinator (Marie Markwell) * Status: Rejected * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: 2.6 ---------------------------------------- =begin On the 'duckinator' branch of my fork of ruby on github, I have added Numeric#divisor?: num.divisor?(other) is the same as: (num % other == 0) Example usage: 4.divisor?(2) #=> true 1.divisor?(2) #=> false 2.4.divisor?(1.2) #=> true 2.4.divisor?(1.3) #=> false 126.divisor?(9) #=> true I think this would be a very nice feature to add, and would make code using the old (num % other == 0) method much cleaner and easier to understand. There is a unified diff of it: http://gist.github.com/raw/484144/07b1a6e696cd9301e658ccbc8f90dfcd4d4ef3f1/… The original commits can be seen here: http://github.com/RockerMONO/ruby/commit/f7959f964cb0bf38418904ccb5643db6b6… -- First attempt, only worked with Integers http://github.com/RockerMONO/ruby/commit/12376a6bb1c3ffbd4b470850dd758e2dcd… -- Second attempt, should work with anything derived from Numeric that can be used as (num % other == 0) =end -- https://bugs.ruby-lang.org/

1 0