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

[ruby-core:111450] [Ruby master Bug#19268] Mingw64 Build Failure
by cfis (Charlie Savage) 31 Dec '24

31 Dec '24

Issue #19268 has been reported by cfis (Charlie Savage). ---------------------------------------- Bug #19268: Mingw64 Build Failure https://bugs.ruby-lang.org/issues/19268 * Author: cfis (Charlie Savage) * 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, 3.2: UNKNOWN ---------------------------------------- For both Ruby 3.1.3 and Ruby 3.2.0, building on msys2/ucrt64 fails: ``` c linking miniruby.exe /usr/bin/sh: -c: line 1: syntax error near unexpected token `(' /usr/bin/sh: -c: line 1: `/usr/local/ruby/bin/ruby --disable=gems -n -e BEGIN{version=ARGV.shift;mis=ARGV.dup} -e END{abort "UNICODE version mismatch: #{mis}" unless mis.empty?} -e (mis.delete(ARGF.path); ARGF.close) if /ONIG_UNICODE_VERSION_STRING +"#{Regexp.quote(version)}"/o 15.0.0 ./enc/unicode/15.0.0/casefold.h ./enc/unicode/15.0.0/name2ctype.h' make: *** [uncommon.mk:878: .rbconfig.time] Error 2 ``` The fix that works for me is changing: ``` c -e '(mis.delete(ARGF.path); ARGF.close) if /ONIG_UNICODE_VERSION_STRING +"#{Regexp.quote(version)}"/o' \ ``` To ``` c -e "(mis.delete(ARGF.path); ARGF.close) if /ONIG_UNICODE_VERSION_STRING +\"#{Regexp.quote(version)}\"/o" \ ``` ``` -- https://bugs.ruby-lang.org/

1 4

[ruby-core:120448] [Ruby master Bug#20994] C API - How to Create Classes with Non-ASCII characters in Name
by cfis (Charlie Savage) 30 Dec '24

30 Dec '24

Issue #20994 has been reported by cfis (Charlie Savage). ---------------------------------------- Bug #20994: C API - How to Create Classes with Non-ASCII characters in Name https://bugs.ruby-lang.org/issues/20994 * Author: cfis (Charlie Savage) * Status: Open * ruby -v: ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [x64-mswin64_140] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- As part of Rice (Ruby C++ bindings), I am experimenting with using unicode characters to make more readable class names (see https://ruby-rice.github.io/4.x/stl/stl.html#automatically-generated-ruby-c…) I am experimenting with class names like this: ``` Map≺string≺char≻٬vector≺complex≺double≻≻≻` ``` Where < and > are actually Unicode characters precede (\u227A) and succeed (\u227B). In Ruby this works fine: ``` ruby irb(main):01> class Map≺string≺char≻٬vector≺complex≺double≻≻≻ irb(main):02> end => nil irb(main):013> Map≺string≺char≻٬vector≺complex≺double≻≻≻.new => #<Map≺string≺char≻٬vector≺complex≺double≻≻≻:0x0000021114674c98> ``` However, this fails using the Ruby C API `define_method`. Passing a `char*` that is utf8 encoded fails because `define_method` calls `rb_intern` which calls `rb_intern2` which forces the use of ascii encoding (see https://github.com/ruby/ruby/blob/5fec9308320e8b377681ef19b0cd46d53f94e8ac/…) I thought I might be able to define the class using ascii characters, and then call `rb_define_const` to add in a utf8 encoded name, but that also has the same problem. My question - how does one create class names that have non ascii characters in them via the C API? -- https://bugs.ruby-lang.org/

2 3

[ruby-core:116009] [Ruby master Bug#20147] FreeBSD libyaml
by kaiquekandykoga 30 Dec '24

30 Dec '24

Issue #20147 has been reported by kaiquekandykoga (Kaíque Koga). ---------------------------------------- Bug #20147: FreeBSD libyaml https://bugs.ruby-lang.org/issues/20147 * Author: kaiquekandykoga (Kaíque Koga) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I use ruby-install to manage multiple Ruby versions. Some time ago I had issues installing Ruby 3.2.2 https://github.com/postmodern/ruby-install/issues/463, and the same issue was open for ruby-build in https://github.com/rbenv/ruby-build/issues/2184. I am trying to install Ruby 3.3.0 using ruby-install, and the same behaviour is occurring. Please, take a look in the links I have provided for detailed information. ``` shell /usr/home/kandy/src/ruby-3.3.0/lib/yaml.rb:3: warning: It seems your ruby installation is missing psych (for YAML output). To eliminate this warning, please install libyaml and reinstall your ruby. uh-oh! RDoc had a problem: cannot load such file -- psych run with --debug for full backtrace *** Error code 1 Stop. make: stopped in /usr/home/kandy/src/ruby-3.3.0 !!! Compiling ruby 3.3.0 failed! ``` Thank you. -- https://bugs.ruby-lang.org/

3 6

[ruby-core:120174] [Ruby master Bug#20943] Constant defined in `Data` block
by nobu (Nobuyoshi Nakada) 30 Dec '24

30 Dec '24

Issue #20943 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Bug #20943: Constant defined in `Data` block https://bugs.ruby-lang.org/issues/20943 * Author: nobu (Nobuyoshi Nakada) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- From https://github.com/ruby/ruby/pull/12274: > A couple times in code review I've seen constants inadvertently leak to top level from within a `Struct` or `Data` do block. I think it would be nice to show reopening the `Data` class when a constant is defined, so the constant is defined within the namespace. In this case, `Measure::NONE` instead of top level `Object::NONE`. It would also show readers that it's okay to reopen a `Data` class, which seems nice since some folk might not realize. Thanks for considering! However, I think that `NONE` probably might be intended to be defined under `Measure`. Current: ```ruby Measure = Data.define(:amount, :unit) do NONE = Data.define end p NONE #=> NONE ``` Another: ```ruby Measure = Data.define(:amount, :unit) do NONE = Data.define p NONE #=> Measure::NONE end p NONE # uninitialized constant NONE (NameError) ``` @zverok How do think? -- https://bugs.ruby-lang.org/

7 7

[ruby-core:120431] [Ruby master Bug#20988] String literal that includes `\C-` `\M-` with `\111` wrongly parsed
by tompng (tomoya ishida) 28 Dec '24

28 Dec '24

Issue #20988 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #20988: String literal that includes `\C-` `\M-` with `\111` wrongly parsed https://bugs.ruby-lang.org/issues/20988 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.5.0dev (2024-12-27T07:27:30Z master adbbc9109e) +YJIT +MN +PRISM [arm64-darwin22] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Prism and parse.y parses this string literal differently. ~~~ $ ./ruby -e 'p "\C-\111 \M-\111 \M-\C-\111"' "I I I" ~~~ ~~~ $ ./ruby --parser=parse.y -e 'p "\C-\111 \M-\111 \M-\C-\111"' "\t \xC9 \x89" ~~~ -- https://bugs.ruby-lang.org/

2 1

[ruby-core:120437] [Ruby master Bug#20991] Prism parses `"\C-\α"` into `"α"` which should be syntax error
by tompng (tomoya ishida) 28 Dec '24

28 Dec '24

Issue #20991 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #20991: Prism parses `"\C-\α"` into `"α"` which should be syntax error https://bugs.ruby-lang.org/issues/20991 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.5.0dev (2024-12-27T07:27:30Z master adbbc9109e) +YJIT +MN +PRISM [arm64-darwin22] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ~~~ $ ./ruby -e 'p "\C-\α"' "α" ~~~ I think it should raise `Invalid escape character syntax` just like `"\C-α"` does. ~~~ruby "\C-α" # Invalid escape character syntax "\C-\α" # Prism: "α" # parse.y: invalid multibyte char (UTF-8), reported in #20990 ~~~ -- https://bugs.ruby-lang.org/

1 1

[ruby-core:120435] [Ruby master Bug#20990] Ripper.tokenize splits `"\C-\あ"` into tokens with invalid byte sequence
by tompng (tomoya ishida) 28 Dec '24

28 Dec '24

Issue #20990 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #20990: Ripper.tokenize splits `"\C-\あ"` into tokens with invalid byte sequence https://bugs.ruby-lang.org/issues/20990 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT +MN [arm64-darwin22] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- IRB crashes when a code is tokenized to an invalid byte sequence. ~~~ruby Ripper.tokenize '"\C-\あ"' #=> ["\"", "\\C-\\\xE3\x81", "\x82", "\""] ~~~ I think the error evaluating `"\C-\あ"` should be `Invalid escape character syntax` just like `"\C-あ"` ~~~ $ ./ruby --parser=parse.y -e '"\C-あ"' -e:1: Invalid escape character syntax "\C-あ" $ ./ruby --parser=parse.y -e '"\C-\あ"' -e:1: invalid multibyte char (UTF-8) -e:1: invalid multibyte char (UTF-8) ./ruby: compile error (SyntaxError) ~~~ -- https://bugs.ruby-lang.org/

1 1

[ruby-core:119534] [Ruby master Bug#20800] Don't place `ruby` executable into `/usr/libexec/x86_64-linux/bin`
by vo.x (Vit Ondruch) 27 Dec '24

27 Dec '24

Issue #20800 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #20800: Don't place `ruby` executable into `/usr/libexec/x86_64-linux/bin` https://bugs.ruby-lang.org/issues/20800 * Author: vo.x (Vit Ondruch) * Status: Open * ruby -v: ruby 3.4.0dev (2024-10-15 master 3da3cabf98) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Trying to prepare Ruby 3.4 package for Fedora, it seems that since [1], the `ruby` executable is installed into `/usr/libexec/x86_64-linux/bin`: ~~~ installing binary commands: /usr/libexec/x86_64-linux/bin ~~~ Unfortunately, the PR does not explain anything about reasons why. To me, using `libexec` is surprising, because according to FHS [2], the directory is for internal binaries. What is even more surprising is usage of the `bin` subdirectory there, which IMHO does not follow any standard or convention (I don't have `/usr/libexec/x86_64-linux/bin` directory on my Fedora yet). Just FTR, these are the configuration options used: ~~~ /builddir/build/BUILD/ruby-3.4.0_20241016git3da3cabf98-build/ruby-3.4.0-3da3cabf98/configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --runstatedir=/run --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-rubylibprefix=/usr/share/ruby --with-archlibdir=/usr/lib64 --with-rubyarchprefix=/usr/lib64/ruby --with-sitedir=/usr/local/share/ruby/site_ruby --with-sitearchdir=/usr/local/lib64/ruby/site_ruby --with-vendordir=/usr/share/ruby/vendor_ruby --with-vendorarchdir=/usr/lib64/ruby/vendor_ruby --with-rubyhdrdir=/usr/include --with-rubyarchhdrdir=/usr/include '--with-sitearchhdrdir=$(sitehdrdir)/$(arch)' '--with-vendorarchhdrdir=$(vendorhdrdir)/$(arch)' --with-rubygemsdir=/usr/share/rubygems --with-ruby-pc=ruby.pc --with-compress-debug-sections=no --disable-rpath --enable-mkmf-verbose --enable-shared --with-ruby-version= --enable-multiarch --enable-yjit ~~~ The `--enable-multiarch` is among the options. It is used not because Fedora would be `multiarch`, but because it provides the highest flexibility. [1]: https://github.com/ruby/ruby/pull/10010 [2]: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html -- https://bugs.ruby-lang.org/

4 9

[ruby-core:120423] [Ruby master Bug#20986] Bug in Prism parser with `?\C`
by tenderlovemaking (Aaron Patterson) 26 Dec '24

26 Dec '24

Issue #20986 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Bug #20986: Bug in Prism parser with `?\C` https://bugs.ruby-lang.org/issues/20986 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Assignee: prism * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Prism output is this: ``` $ ./miniruby -e 'p ?\C-\]' "]" ``` Parse.y output is this: ``` $ ./miniruby --parser=parse.y -e 'p ?\C-\]' "\u001D" ``` -- https://bugs.ruby-lang.org/

3 2

[ruby-core:120147] [Ruby master Bug#20939] When using the parse.y parser, it occurs argument stack underflow (-1) if there is processing after the shareable_constant_value: experimental_everything comment and `C = { **{ k: v } }`
by ydah (Yudai Takada) 26 Dec '24

26 Dec '24

Issue #20939 has been reported by ydah (Yudai Takada). ---------------------------------------- Bug #20939: When using the parse.y parser, it occurs argument stack underflow (-1) if there is processing after the shareable_constant_value: experimental_everything comment and `C = { **{ k: v } }` https://bugs.ruby-lang.org/issues/20939 * Author: ydah (Yudai Takada) * Status: Open * ruby -v: ruby 3.4.0dev (2024-12-10T03:31:47Z master f12e2622c1) [arm64-darwin23] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- The following code will occurs argument stack underflow if it is a parse.y parser. ```ruby # shareable_constant_value: experimental_everything C = { **{ k: v } } p C ``` The following error message is output. ``` ruby 3.4.0dev (2024-12-06T03:32:20Z master 6ccaa37eb3) [arm64-darwin23] -- raw disasm-------- trace: 1 0000 putspecialobject 1 ( 2) 0002 putobject :k ( 2) 0004 putself ( 2) 0005 opt_send_without_block <calldata:v, 0> ( 2) 0007 newhash 2 ( 2) 0009 newhash 2 ( 2) 0011 opt_send_without_block <calldata:make_shareable, 1> ( 2) 0013 putspecialobject 3 ( 2) * 0015 setconstant :C ( 2) trace: 1 0017 putself ( 3) 0018 opt_getconstant_path [:C] ( 3) 0020 opt_send_without_block <calldata:p, 1> ( 3) 0022 leave ( 3) --------------------- -e:2: argument stack underflow (-1) -e: compile error (SyntaxError) ``` It does not occur in the following cases: ```ruby # shareable_constant_value: experimental_everything C = { **{ k: v } } ``` ```ruby C = { **{ k: v } } p C ``` ```ruby # shareable_constant_value: experimental_everything { **{ k: v } } p C ``` ```ruby # shareable_constant_value: experimental_everything C = { **{ k: 1 } } p C ``` This does not occur in Ruby 3.3: ``` ❯ ruby --parser=parse.y -v -e '# shareable_constant_value: experimental_everything C = { **{ foo: bar } } p C' ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [arm64-darwin23] -e:3:in `<main>': undefined local variable or method `bar' for main (NameError) C = { **{ foo: bar } } ^^^ ``` -- https://bugs.ruby-lang.org/

2 2