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

[ruby-core:118779] [Ruby master Bug#20662] pack("g") completely discards any actual NaN value and always packs the same single-precision bytes for a NaN
by cabo (Carsten Bormann) 13 Aug '24

13 Aug '24

Issue #20662 has been reported by cabo (Carsten Bormann). ---------------------------------------- Bug #20662: pack("g") completely discards any actual NaN value and always packs the same single-precision bytes for a NaN https://bugs.ruby-lang.org/issues/20662 * Author: cabo (Carsten Bormann) * Status: Open * ruby -v: ruby 3.3.4 (2024-07-09 revision be1089c8ec) [arm64-darwin23] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- pack("G")/unpack("G") works great with NaN values. However, # - pack("g") completely discards any actual NaN value and always packs the same bytes for a NaN # ("bug as implemented" in VALUE_to_float) Also: # - unpack("g") always sets the quiet bit to 1 in the Float result # (location of bug not obvious to me) ---Files-------------------------------- showbug.rb (3.21 KB) showbug-arm.txt (5.48 KB) showbug-intel.txt (5.48 KB) -- https://bugs.ruby-lang.org/

2 4

[ruby-core:118826] [Ruby master Bug#20671] Do not show "unused block" warning on `send`
by ko1 (Koichi Sasada) 13 Aug '24

13 Aug '24

Issue #20671 has been reported by ko1 (Koichi Sasada). ---------------------------------------- Bug #20671: Do not show "unused block" warning on `send` https://bugs.ruby-lang.org/issues/20671 * Author: ko1 (Koichi Sasada) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Let's disable "unused block" warning on `send` because now it is hard to recognize the calling method accepts a block or not for general framework. Now test/unit has this problem. ```ruby require 'test/unit' class T < Test::Unit::TestCase def setup end def test_foo = nil end #=> /home/ko1/ruby/install/master/lib/ruby/gems/3.4.0+0/gems/test-unit-3.6.2/lib/test/unit/fixture.rb:284: warning: the block passed to 'priority_setup' defined at /home/ko1/ruby/install/master/lib/ruby/gems/3.4.0+0/gems/test-unit-3.6.2/lib/test/unit/priority.rb:183 may be ignored ``` Implementation: https://github.com/ruby/ruby/pull/11349 I think we can revisit it when we provide a way to recognize the calling method may accept a block or not. But now the relaxed behavior is better I think. -- https://bugs.ruby-lang.org/

1 1

[ruby-core:118834] New webmail message
by Noreply＠ruby-lang.org 12 Aug '24

12 Aug '24

1 0

[ruby-core:118791] [Ruby master Bug#20666] Segmentation fault instead of LoadError exception
by ErezGeva2＠gmail.com (Erez Geva) 11 Aug '24

11 Aug '24

Issue #20666 has been reported by ErezGeva2(a)gmail.com (Erez Geva). ---------------------------------------- Bug #20666: Segmentation fault instead of LoadError exception https://bugs.ruby-lang.org/issues/20666 * Author: ErezGeva2(a)gmail.com (Erez Geva) * Status: Open * ruby -v: ruby 3.2.5 (2024-07-26 revision 31d0f1a2e7) [x64-mingw-ucrt] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Using ruby -v ruby 3.2.5 (2024-07-26 revision 31d0f1a2e7) [x64-mingw-ucrt] From [GitHub windows 2022](https://github.com/actions/runner-images/blob/main/images/windows/Win… ) We run the SWIG test: [import_fragments](https://github.com/swig/swig/blob/master/Examples/test-su… The test try to load a broken library, which should rise a `LoadError`. begin require 'import_fragments' rescue LoadError => e # due to missing import_fragments_a exception_file = e.respond_to?(:path) ? e.path : e.to_s.sub(/.* -- /, '') end Instead `LoadError` exception we get `Segmentation fault`: <internal:C:/hostedtoolcache/windows/Ruby/3.2.5/x64/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:151: [BUG] Segmentation fault ruby 3.2.5 (2024-07-26 revision 31d0f1a2e7) [x64-mingw-ucrt] -- Control frame information ----------------------------------------------- c:0004 p:0018 s:0028 e:000025 RESCUE <internal:C:/hostedtoolcache/windows/Ruby/3.2.5/x64/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:151 c:0003 p:0275 s:0022 e:000021 METHOD <internal:C:/hostedtoolcache/windows/Ruby/3.2.5/x64/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:40 c:0002 p:0011 s:0007 E:0004e8 EVAL ./import_fragments_runme.rb:13 [FINISH] c:0001 p:0000 s:0003 E:0006e0 DUMMY [FINISH] -- https://bugs.ruby-lang.org/

2 8

[ruby-core:118827] [Ruby master Bug#20672] UNIXSocket.pair transmitting data between pids looks flaky
by danh337 (Dan H) 10 Aug '24

10 Aug '24

Issue #20672 has been reported by danh337 (Dan H). ---------------------------------------- Bug #20672: UNIXSocket.pair transmitting data between pids looks flaky https://bugs.ruby-lang.org/issues/20672 * Author: danh337 (Dan H) * Status: Open * ruby -v: ruby 3.3.4 (2024-07-09 revision be1089c8ec) [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I have code that uses UNIXSocket.pair and fork to send data between parent and child. It seems to work fine for a small number of messages passed, but then fails with Errno::EBADF on the child pid writing to its socket received from the parent. I attached a test driver which includes successful and failed test runs. This is boiled down logic from a larger app, where I first started seeing this issue. I believe I first saw this on Ruby 3.0, but now I am on 3.3.4. This *could* be me, as in my code or my workstation env, but I have not been able to prove that from many web searches. If you look at my test driver and see something wrong with it, I will take the shame and learn something. BUT just in case this is an issue in low level Ruby code, I am submitting this here. ---Files-------------------------------- test.rb (13 KB) -- https://bugs.ruby-lang.org/

2 3

[ruby-core:118782] [Ruby master Bug#20663] Reading from IO does not recover gracefully from bad data pushed via IO#ungetc
by javanthropus (Jeremy Bopp) 09 Aug '24

09 Aug '24

Issue #20663 has been reported by javanthropus (Jeremy Bopp). ---------------------------------------- Bug #20663: Reading from IO does not recover gracefully from bad data pushed via IO#ungetc https://bugs.ruby-lang.org/issues/20663 * Author: javanthropus (Jeremy Bopp) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- If bytes that result in at least 2 invalid characters for the internal encoding of an IO object are pushed into the internal buffer with IO#getc, reading from the stream returns invalid characters composed of both bytes from the internal buffer and the converted bytes from the stream even if the next character in the stream itself is completely valid. ``` ruby char_bytes = Tempfile.open(encoding: 'utf-8:utf-16le') do |f| f.write("🍣") f.rewind f.ungetc("🍣".encode('utf-16le').b[0..-2]) f.each_char.map(&:bytes) end puts char_bytes.inspect ``` The above outputs: ``` [[60, 216], [99, 60], [216, 99], [223]] ``` I expect it to output: ``` [[60, 216], [99], [60, 216, 99, 223]] ``` In other words, I expect it to first completely drain the internal character buffer returning as many characters as necessary (invalid or otherwise) before reading from the stream and converting and returning the next character. Interestingly, if there are only bytes sufficient for 1 invalid character in the internal buffer, it behaves that way: ``` ruby char_bytes = Tempfile.open(encoding: 'utf-8:utf-16le') do |f| f.write("🍣") f.rewind f.ungetc("🍣".encode('utf-16le').b[0..-3]) # <- Note the -3 here vs. the -2 earlier f.each_char.map(&:bytes) end puts char_bytes.inspect ``` This outputs: ``` [[60, 216], [60, 216, 99, 223]] ``` The first character is invalid, but returning it first clears the buffer. Then the next character is read, converted, and returned in full. -- https://bugs.ruby-lang.org/

1 1

[ruby-core:118588] [Ruby master Bug#20634] ruby uses 1/2 (7 out of 16) cores for 16 ractors with RUBY_MAX_CPU=16 environment variable set
by skorobogatydmitry (Dmitry Skorobogaty) 09 Aug '24

09 Aug '24

Issue #20634 has been reported by skorobogatydmitry (Dmitry Skorobogaty). ---------------------------------------- Bug #20634: ruby uses 1/2 (7 out of 16) cores for 16 ractors with RUBY_MAX_CPU=16 environment variable set https://bugs.ruby-lang.org/issues/20634 * Author: skorobogatydmitry (Dmitry Skorobogaty) * Status: Open * ruby -v: ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- It's a cont for #20618, feel free to close this one and reopen the original bug. According to `top`, the below code uses 7/16 cores (700%) of my AMD Ryzen 7 5800HS: #!/usr/bin/env ruby 16.times { Ractor.new { 10_000.downto(1) { |i| 100_000.downto(1) { |j| i * j } } } } sleep 30 ``` Command I ran is `RUBY_MAX_CPU=16 ruby test.rb`. I also tried to set `RUBY_MN_THREADS=1` as an addition and the script starts to occupy 8 cores instead of 7 (possibly, due to N:M algo allocating an extra core for the blocked main Ractor). The same code occupies all 16 cores on ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux] The problem reproduces on ruby 3.3.3 (2024-06-12 revision f1c7b6f435) [x86_64-linux] (ruby from the latest docker image). -- https://bugs.ruby-lang.org/

1 2

[ruby-core:118789] [Ruby master Bug#20665] Swig testing of Ruby with MinGW-w64 UCRT
by ErezGeva2＠gmail.com (Erez Geva) 07 Aug '24

07 Aug '24

Issue #20665 has been reported by ErezGeva2(a)gmail.com (Erez Geva). ---------------------------------------- Bug #20665: Swig testing of Ruby with MinGW-w64 UCRT https://bugs.ruby-lang.org/issues/20665 * Author: ErezGeva2(a)gmail.com (Erez Geva) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Hi, I try to add SWIG project testing with already installed Ruby on [GitHub Windows2022](https://github.com/actions/runner-images/blob/main/images/wind…. I manage to test with Ruby version 3.0.7 and installed mingw-w64-x86_64-ruby version 3.1.5. Both are build with MinGW-w64. See: https://github.com/swig/swig/pull/2981 Now I want to use the more newer Ruby. GitHub Windows2022 provides 2 Ruby version 3.1.6 and 3.2.5 which are build with MinGW-w64 UCRT. I try and use mingw-w64-ucrt-x86_64-gcc with more mingw-w64-ucrt-x86_64-XXX packages. My testing can be found here: https://github.com/erezgeva/swig/blob/win_ruby2/.github/workflows/windows.y… The test fails: https://github.com/erezgeva/swig/actions/runs/10237377988/job/28320593017 Can you advice what is wrong here? Erez -- https://bugs.ruby-lang.org/

2 4

[ruby-core:118520] [Ruby master Feature#20621] Check libruby.so hardening by annocheck
by vo.x (Vit Ondruch) 07 Aug '24

07 Aug '24

Issue #20621 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Feature #20621: Check libruby.so hardening by annocheck https://bugs.ruby-lang.org/issues/20621 * Author: vo.x (Vit Ondruch) * Status: Open ---------------------------------------- As part of #18061, there was implemented annocheck test case. However, the test covers just `ruby` (which is just thin shell), while leaves out `libruby.so` (which contains most of the Ruby code). This PR tries to improve that: https://github.com/ruby/ruby/pull/11123 BTW the question is if all *.so files or even all *.o files should be covered. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:118802] [Ruby master Feature#17166] net/http not supporting unix domain sockets
by kddnewton (Kevin Newton) 06 Aug '24

06 Aug '24

Issue #17166 has been updated by kddnewton (Kevin Newton). Then build it. If it’s as widely used as you say, the PR is sure to be accepted. ---------------------------------------- Feature #17166: net/http not supporting unix domain sockets https://bugs.ruby-lang.org/issues/17166#change-109358 * Author: hadmut (Hadmut Danisch) * Status: Third Party's Issue ---------------------------------------- Hi, meanwhile it's common and state of the art to offer rest apis not just over tcp/ip, but over unix domain sockets as well for machine-internal use and advanced security. Unfortunately net/http does not support unix domain sockets. Although there is a workaround with the gem net_http_unix / NetX::HTTPUnix, this is rather useless, since most programs, libs, gems (e.g. rest-client) are based on net/http. However, there's some security consideration. When evaluating e.g. HTML and accessing URLs, it could be harmful or leak information, if an URL point to some unix domain path could reveal information or allow to trigger something, e.g. tell through error messages whether a file exists or let someone unintentionally install a packet through ubuntu's snap mechanism (which is controlled through a unix domain socket with rest api). It should, however, be possible to use unix domain sockets (without workaround, third party gem or low level code). regards -- https://bugs.ruby-lang.org/

1 0