December 2022 - ruby-core - ml.ruby-lang.org

[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:111318] [Ruby master Misc#19240] DevMeeting-2023-01-19
by mame (Yusuke Endoh) 16 Jan '23

16 Jan '23

Issue #19240 has been reported by mame (Yusuke Endoh). ---------------------------------------- Misc #19240: DevMeeting-2023-01-19 https://bugs.ruby-lang.org/issues/19240 * Author: mame (Yusuke Endoh) * Status: Open * Priority: Normal ---------------------------------------- # The next dev meeting **Date: 2023/01/19 13:00-17:00** (JST) Log: *TBD* - Dev meeting *IS NOT* a decision-making place. All decisions should be done at the bug tracker. - Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly. - Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue). - We will write a record of the discussion in the file or to each ticket in English. - All activities are best-effort (keep in mind that most of us are volunteer developers). - The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time. - *DO NOT* discuss then on this ticket, please. # Call for agenda items If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format: ``` * [Ticket ref] Ticket title (your name) * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.) ``` Example: ``` * [Feature #14609] `Kernel#p` without args shows the receiver (ko1) * I feel this feature is very useful and some people say :+1: so let discuss this feature. ``` - It is recommended to add a comment by 2023/01/16. We hold a preparatory meeting to create an agenda a few days before the dev-meeting. - The format is strict. We'll use [this script to automatically create an markdown-style agenda](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). We may ignore a comment that does not follow the format. - Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion. -- https://bugs.ruby-lang.org/

10 13

[ruby-core:111400] [Ruby master Bug#19254] Enabling YJIT configuration option breaks rspec-core test suite
by vo.x (Vit Ondruch) 11 Jan '23

11 Jan '23

Issue #19254 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #19254: Enabling YJIT configuration option breaks rspec-core test suite https://bugs.ruby-lang.org/issues/19254 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0dev (2022-12-23 master c5eefb7f37) [x86_64-linux] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- In preparation for Ruby 3.2, we have enabled YJIT in Fedora: https://src.fedoraproject.org/rpms/ruby/c/3c1be9f9c2c1d8679eebb9a185fefa15b… Since that moment, rspec-core test suite started to fail (see the attached log for all details): ~~~ ... snip ... 1) RSpec::Core::Example#run memory leaks, see GH-321, GH-1921 releases references to the examples / their ivars Failure/Error: expect(get_all.call).to eq opts.fetch(:post_gc) expected: [] got: ["after_all", "before_all"] (compared using ==) # ./spec/rspec/core/example_spec.rb:469:in `expect_gc' # ./spec/rspec/core/example_spec.rb:492:in `block (4 levels) in <top (required)>' # ./spec/support/sandboxing.rb:16:in `block (3 levels) in <top (required)>' # ./spec/support/sandboxing.rb:7:in `block (2 levels) in <top (required)>' Finished in 8.98 seconds (files took 0.47612 seconds to load) 2209 examples, 1 failure, 4 pending ~~~ Please note that the YJIT was not enabled during runtime, just the support was enabled. Disabling the YJIT supports makes the test case pass. [1]: https://download.copr.fedorainfracloud.org/results/vondruch/ruby-3.2/fedora… [2]: https://copr.fedorainfracloud.org/coprs/vondruch/ruby-3.2/package/rubygem-r… ---Files-------------------------------- builder-live.log.gz (28.7 KB) -- https://bugs.ruby-lang.org/

5 6

[ruby-core:111402] [Ruby master Bug#19255] YJIT: global symbol leakage
by nobu (Nobuyoshi Nakada) 10 Jan '23

10 Jan '23

Issue #19255 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Bug #19255: YJIT: global symbol leakage https://bugs.ruby-lang.org/issues/19255 * Author: nobu (Nobuyoshi Nakada) * Status: Open * Priority: Normal * Backport: 2.7: DONTNEED, 3.0: DONTNEED, 3.1: DONTNEED ---------------------------------------- When YJIT support is enabled, libyjit.a adds thousands leaking global symbols. With this patch: ```diff diff --git a/template/Makefile.in b/template/Makefile.in index 145631386d8..6191bcbeb88 100644 --- a/template/Makefile.in +++ b/template/Makefile.in @@ -720,5 +720,5 @@ mjit_build_dir.$(SOEXT): $(MJIT_MIN_HEADER) $(srcdir)/ruby-runner.c ruby-runner. $(OUTFLAG)$@ $(srcdir)/ruby-runner.c # yes-test-basic: leaked-globals -leaked-globals: $(COMMONOBJS) prog $(tooldir)/leaked-globals PHONY - $(Q) $(XRUBY) $(tooldir)/leaked-globals NM=$(NM) SYMBOL_PREFIX=$(SYMBOL_PREFIX) PLATFORM=$(hdrdir)/ruby/$(PLATFORM_DIR).h $(srcdir)/configure.ac $(COMMONOBJS) +leaked-globals: $(COMMONOBJS) $(YJIT_LIBS) prog $(tooldir)/leaked-globals PHONY + $(Q) $(XRUBY) $(tooldir)/leaked-globals NM=$(NM) SYMBOL_PREFIX=$(SYMBOL_PREFIX) PLATFORM=$(hdrdir)/ruby/$(PLATFORM_DIR).h $(srcdir)/configure.ac $(COMMONOBJS) $(YJIT_LIBS) ``` `make leaked-globals` reports **2915 un-prefixed symbols leaked**. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:111432] [Ruby master Bug#19260] ruby/spec is failed with Ruby 3.3
by hsbt (Hiroshi SHIBATA) 06 Jan '23

06 Jan '23

Issue #19260 has been reported by hsbt (Hiroshi SHIBATA). ---------------------------------------- Bug #19260: ruby/spec is failed with Ruby 3.3 https://bugs.ruby-lang.org/issues/19260 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- After bumping version, we got the some fails with ruby/spec. https://github.com/ruby/ruby/actions/runs/3778576412/jobs/6423166914 ``` 1) Literal Regexps handles a lookbehind with ss characters ERROR RegexpError: invalid pattern in look-behind: /(?<!dss)/i /home/runner/work/ruby/ruby/src/spec/ruby/language/regexp_spec.rb:120:in `block (3 levels) in <top (required)>' /home/runner/work/ruby/ruby/src/spec/ruby/language/regexp_spec.rb:4:in `<top (required)>' 2) Float#round does not lose precision during the rounding process FAILED Expected 767573.18758 to have same value and type as 767573.18759 /home/runner/work/ruby/ruby/src/spec/ruby/core/float/round_spec.rb:148:in `block (3 levels) in <top (required)>' /home/runner/work/ruby/ruby/src/spec/ruby/core/float/round_spec.rb:3:in `<top (required)>' 3) Encoding#replicate has been removed FAILED Expected #<Encoding:US-ASCII>.respond_to? :replicate, true to be falsy but was true /home/runner/work/ruby/ruby/src/spec/ruby/core/encoding/replicate_spec.rb:72:in `block (3 levels) in <top (required)>' /home/runner/work/ruby/ruby/src/spec/ruby/core/encoding/replicate_spec.rb:4:in `<top (required)>' ``` -- https://bugs.ruby-lang.org/

3 5

[ruby-core:111477] [Ruby master Bug#19275] Bundled gems extensions are not installed with 3.2.0 release tarball
by xtkoba (Tee KOBAYASHI) 05 Jan '23

05 Jan '23

Issue #19275 has been reported by xtkoba (Tee KOBAYASHI). ---------------------------------------- Bug #19275: Bundled gems extensions are not installed with 3.2.0 release tarball https://bugs.ruby-lang.org/issues/19275 * Author: xtkoba (Tee KOBAYASHI) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [aarch64-linux-android] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Bundled gems extensions are not installed with 3.2.0 release tarball when cross building for `aarch64-linux-android` target. Possibly related to #19271. Excerpt from build log: ``` 2022-12-28T12:39:39.5065133Z linking shared-object rbs_extension.so 2022-12-28T12:39:39.5317220Z Successfully remade target file '../../../../../.bundle/extensions/aarch64-linux-android/3.2.0/rbs-2.8.2/rbs_extension.so'. [...] 2022-12-28T12:40:06.9333744Z rm -rf .bundle/extensions/aarch64-linux-android/ ``` Seems like bundled gems extensions are built but removed afterwards. The workaround we took is to patch `common.mk` so that `outdate-bundled-gems` is not triggered: ```patch --- a/common.mk +++ b/common.mk @@ -1375,7 +1375,6 @@ refresh-gems: update-bundled_gems prepare-gems prepare-gems: $(HAVE_BASERUBY:yes=update-gems) $(HAVE_BASERUBY:yes=extract-gems) -prepare-gems: $(DOT_WAIT) $(HAVE_BASERUBY:yes=outdate-bundled-gems) extract-gems: $(HAVE_BASERUBY:yes=update-gems) update-gems$(gnumake:yes=-sequential): PHONY ``` Full build log is attached. ---Files-------------------------------- build.log.xz (245 KB) -- https://bugs.ruby-lang.org/

3 7

[ruby-core:111010] [Ruby master Bug#19150] pack/unpack silently ignores unknown directives
by Eregon (Benoit Daloze) 05 Jan '23

05 Jan '23

Issue #19150 has been reported by Eregon (Benoit Daloze). ---------------------------------------- Bug #19150: pack/unpack silently ignores unknown directives https://bugs.ruby-lang.org/issues/19150 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- But I believe it should be an error instead. Typically when a parser sees a syntax error it should fail not continue silently. For instance `[1].pack('<L')` succeeds and only emits a warning if `$VERBOSE` is true. This behavior caused confusion in https://github.com/oracle/truffleruby/issues/2791 I think it should fail with an `ArgumentError` instead. Extracted from https://bugs.ruby-lang.org/issues/19108#note-3 -- https://bugs.ruby-lang.org/

4 4

[ruby-core:111451] [Ruby master Bug#19269] Constant lookup and #instance_eval
by andrykonchin (Andrew Konchin) 04 Jan '23

04 Jan '23

Issue #19269 has been reported by andrykonchin (Andrew Konchin). ---------------------------------------- Bug #19269: Constant lookup and #instance_eval https://bugs.ruby-lang.org/issues/19269 * 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 a confusing behaviour of `#instance_eval` (and `#instance_exec` as well). In some cases it doesn't see constants defined in the object class. Examples: ```ruby C = 1 class A C = 2 end ``` When `#instance_eval` is called with a String - `A::C` constant is visible, that is pretty expected: ```ruby A.new.instance_eval("C") # => 2 ``` But when it's called with a block - `A::C` isn't visible: ```ruby A.new.instance_eval { C } # => 1 ``` If we define a method that returns a constant (defined in the class), then `A::C` is visible in both cases: ```ruby C = 1 class A C = 2 def c; C; end end A.new.instance_eval("c") # => 2 A.new.instance_eval { c } # => 2 ``` So we see that when `#instance_eval` called with a block and a constant is assessed directly is the only case when a class constant isn't visible. Wondering whether it's an expected behaviour and the reason to behave this way. -- https://bugs.ruby-lang.org/

3 3

[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