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

[ruby-core:118556] [Ruby master Misc#20628] DevMeeting-2024-08-01
by mame (Yusuke Endoh) 26 Jul '24

26 Jul '24

Issue #20628 has been reported by mame (Yusuke Endoh). ---------------------------------------- Misc #20628: DevMeeting-2024-08-01 https://bugs.ruby-lang.org/issues/20628 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # The next dev meeting **Date: 2024/08/01 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 2024/07/29. 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/

4 3

[ruby-core:118704] Delivery status notification.
by ruby-core＠ruby-lang.org 26 Jul '24

26 Jul '24

こんにちは！ 最初に言わせてください。あなたは唯一無二です！ プロのハッカーという職業柄、色々な物や人を今まで観てきましたが、それでも私はあなたに感心しています。 単刀直入に言いますね。私の言うことをじっくり読んでください。 数カ月前、あなたのオペレーションシステムをハッキングし、お持ちのすべてのデバイスと、メッセンジャーやＳＮＳのプロフィール等、アカウントへのアクセス権を獲得しました。 私のメッセージの意図をご理解いただけたでしょうか。言うまでもなく、キーロガーにあなたが書いたことやネット上の活動、ウェブカメラのストリーミングからアクセス権を獲得しました。 これも全て、悪意のあるマルウェアに感染したアダルトサイトにあなたが頻繁に訪問したことにより、実現しました。つまり数日間、あなたは私の監視下にあったということです。 まるで、顕微鏡で観察されている虫のように。虫とあなたの唯一違う点は、あなたとは違って世界中のどこを探しても、変態趣味のエロビデオを見る虫はいないということでしょう。 そうです。あなたは正しく理解していますね。 あなたのスクリーン上全ての物を私は見ることができ、ビデオを録画したり、カメラやマイクから拾われた音声を聞いたりできています。 録画したものは全て、私のストレージに安全に保存し、バックアップも用意しました。 さらに、メールやチャットメッセージに含まれる重要な機密情報にも私はアクセス可能です。 なぜウイルス対策ソフトやスパイウェアの検知ソフトがなぜ反応しなかったのか気になっているでしょう。 恐縮ですが、そんなのは稚拙な質問です。どのウイルス対策ソフトも、結構前から無駄なアプローチに成り下がっています。 業界でより進んだ最新技術ができたという昨年のニュースを知っていますか？そうです。 最近は開発者はもう、ユーザーの安全性なんて気にしていません。だから私のようなハッカーはその隙間に付け入るんですよ。 この情報を新しく知ったとしても、礼はいりません。この新しい知識があれば、今後はもっと真剣にインターネットの安全性について考え、もう甘い考えは持たないかもしれませんね。 それはさておき、本題に入りましょう。録画した映像を使って、私は総集編ビデオを作成しました。 画面の左側には、あなたが喜んで自慰行為のネタに使った際どいエロ映像、右側にはその動画をみているあなたの様子が表示されます…(*‘ω‘ *) このメールを受け取ってから48時間の猶予を与えます。そのあとは、あなたのメールやメッセンジャーの連絡先全員にビデオを送信します。 しかも、それだけではありません。何だと思います？それは、メールやチャットの履歴を全て公開できちゃうってことです。 かなり強烈なアダルトコンテンツの沼に入られているようですが、別に頭がおかしいわけじゃないでしょう。 だから、こんなことは自分の身に起きてほしくないはずですよね。友人、恋人、家族や同僚がこんなことを一瞬にして知るような状況を喜ぶのは、世界で一番アホなヤツだけでしょうから。 要するに、もう後戻りはできません。どうしようもないんです。 でも、お互いに利益を得られる方法が１つだけあります。私は合理的な人間なので、別にあなたの人生を壊したいとは思っていません。それよりも何か欲しいだけです。 これがあなたの救われる道です ― 1390 USD相当のビットコインを私のビットコインアカウントに送金してください。（方法を知らない場合は、Googleで検索してください） 私のビットコインアドレスは: 1B673aGC1ZMJjm5TSVbpLY1aPu57Xw88YA 送金が確認できれば、全てのビデオを削除し、あなたの人生に二度と現れません。 先ほどお伝えした通り、このメールを開封してから送金完了まで48時間しかありません。 私は常に用意周到ですので、私を騙そうとはしないでください。 このメッセージを誰か別の人と共有したことが分かれば、あなたのビデオをすぐに全員に送信し、ネット上に晒します。 P.S. お互いの関係はあなた次第です。

1 0

[ruby-core:118680] [Ruby master Bug#20650] Memory leak in Regexp capture group when timeout
by peterzhu2118 (Peter Zhu) 25 Jul '24

25 Jul '24

Issue #20650 has been reported by peterzhu2118 (Peter Zhu). ---------------------------------------- Bug #20650: Memory leak in Regexp capture group when timeout https://bugs.ruby-lang.org/issues/20650 * Author: peterzhu2118 (Peter Zhu) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: REQUIRED, 3.3: REQUIRED ---------------------------------------- GitHub PR: https://github.com/ruby/ruby/pull/11238 The capture group allocates memory that is leaked when it times out. For example: ```ruby re = Regexp.new("^#{"(a*)" * 10_000}x$", timeout: 0.000001) str = "a" * 1000000 + "x" 10.times do 100.times do re =~ str rescue Regexp::TimeoutError end puts `ps -o rss= -p #{$$}` end ``` Before: ``` 34688 56416 78288 100368 120784 140704 161904 183568 204320 224800 ``` After: ``` 16288 16288 16880 16896 16912 16928 16944 17184 17184 17200 ``` -- https://bugs.ruby-lang.org/

1 1

[ruby-core:118670] [Ruby master Bug#20647] Invalid return in class/module body from within singleton class
by kddnewton (Kevin Newton) 24 Jul '24

24 Jul '24

Issue #20647 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Bug #20647: Invalid return in class/module body from within singleton class https://bugs.ruby-lang.org/issues/20647 * Author: kddnewton (Kevin Newton) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Currently, Ruby will raise a syntax error for invalid returns within class and module bodies, but skips it for singleton classes. I think we should be able to add this same error for singleton classes, as I believe these always raise a LocalJumpError. ```ruby class << Object return end ``` -- https://bugs.ruby-lang.org/

3 2

[ruby-core:118673] [Ruby master Feature#14919] Add String#byteinsert
by ufuk (Ufuk Kayserilioglu) 23 Jul '24

23 Jul '24

Issue #14919 has been updated by ufuk (Ufuk Kayserilioglu). Given that we now have [`String#bytesplice` since Ruby 3.2](https://bugs.ruby-lang.org/issues/18598), these kinds of operations should be possible using `"xxxxx".bytesplice(byte_pointer, 0, other)` to insert bytes of `other` at `byte_pointer` and `"xxxxx".bytesplice(byte_pointer, num, "")` to remove `num` bytes at `byte_pointer`. ---------------------------------------- Feature #14919: Add String#byteinsert https://bugs.ruby-lang.org/issues/14919#change-109204 * Author: aycabta (aycabta .) * Status: Open ---------------------------------------- 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:118531] [Ruby master Feature#20624] Enhance `RubyVM::AbstractSyntaxTree::Node#locations` method and `RubyVM::AbstractSyntaxTree::Location` class
by yui-knk (Kaneko Yuichiro) 23 Jul '24

23 Jul '24

Issue #20624 has been reported by yui-knk (Kaneko Yuichiro). ---------------------------------------- Feature #20624: Enhance `RubyVM::AbstractSyntaxTree::Node#locations` method and `RubyVM::AbstractSyntaxTree::Location` class https://bugs.ruby-lang.org/issues/20624 * Author: yui-knk (Kaneko Yuichiro) * Status: Open ---------------------------------------- # Background It's revealed that single location information is not enough for some node types. For example, `Prism::IfNode` include these locations * `if_keyword_loc` * `then_keyword_loc` * `end_keyword_loc` * `location` (this is whole node location) I propose `RubyVM::AbstractSyntaxTree::Node#locations` method to provide multiple locations information, and `RubyVM::AbstractSyntaxTree::Location` class for location information. # Example ```ruby node = RubyVM::AbstractSyntaxTree.parse("1 + 2") node = node locs = node.locations loc = locs.first p node # => #<RubyVM::AbstractSyntaxTree::Node:SCOPE@1:0-1:5> p loc.class # => RubyVM::AbstractSyntaxTree::Location p [loc.first_lineno, loc.first_column, loc.last_lineno, loc.last_column] # => [1, 0, 1, 5] ``` # Interface * Add `RubyVM::AbstractSyntaxTree::Location` class which has these methods * `#first_lineno` * `#first_column` * `#last_lineno` * `#last_column` * Add `RubyVM::AbstractSyntaxTree::Node#locations` method which returns multiple location information of the node * The first location is same with the whole node location # Implementation https://github.com/yui-knk/ruby/tree/ast_locations -- https://bugs.ruby-lang.org/

3 3

[ruby-core:118660] [Ruby master Feature#20646] Improve Socket.tcp
by shioimm (Misaki Shioi) 23 Jul '24

23 Jul '24

Issue #20646 has been reported by shioimm (Misaki Shioi). ---------------------------------------- Feature #20646: Improve Socket.tcp https://bugs.ruby-lang.org/issues/20646 * Author: shioimm (Misaki Shioi) * Status: Open ---------------------------------------- This is a proposed improvement to `Socket.tcp`, which has implemented Happy Eyeballs version 2 (RFC8305) in [PR9374](https://github.com/ruby/ruby/pull/9374). 1. Background I implemented Happy Eyeballs version 2 (HEv2) for Socket.tcp in PR9374, but several issues have been identified: - `IO.select` waits for name resolution or connection establishment in v46w, but it does not consider the case where both events occur simultaneously when it returns a value. - In this case, Socket.tcp can only capture one event and needs to execute an unnecessary loop to capture the other one, calling `IO.select` one extra time. - `IO.select` waits for both IPv6/IPv4 name resolution (in start), but when it returns a value, it doesn't consider the case where name resolution for both address families is complete. - In this case, `Socket.tcp` can only obtain the addresses of one address family and needs to execute an unnecessary loop obtain the other addresses, calling `IO.select` one extra time. - The consideration for `connect_timeout` was insufficient. After initiating one or more connections, it raises a 'user specified timeout' after the `connect_timeout` period even if there were addresses that have been resolved and have not yet tried to connect. - It does not retry with another address in case of a connection failure. - It executes unnecessary state transitions even when an IP address is passed as the `host` argument. - The regex for IP addresses did not correctly specify the start and end. 2. Proposal & Outcome To overcome the aforementioned issues, this PR introduces the following changes: - Previously, each loop iteration represented a single state transition. This has been changed to execute all processes that meet the execution conditions within a single loop iteration. - This prevents unnecessary repeated loops and calling `IO.select` - Introduced logic to determine the timeout value set for `IO.select`. During the Resolution Delay and Connection Attempt Delay, the user-specified timeout is ignored. Otherwise, the timeout value is set to the larger of `resolv_timeout` and `connect_timeout`. - This ensures that the `connect_timeout` is only detected after attempting to connect to all resolved addresses. - Retry with another address in case of a connection failure. - This prevents unnecessary repeated loops upon connection failure. - Call `tcp_without_fast_fallback` when an IP address is passed as the host argument. - This prevents unnecessary state transitions when an IP address is passed. - Fixed regex for IP addresses. Additionally, the code has been reduced by over 100 lines, and redundancy has been minimized, which is expected to improve readability. 3. Performance No significant performance changes were observed in the happy case before and after the improvement. However, improvements in state transition deficiencies are expected to enhance performance in edge cases. ```ruby require 'socket' require 'benchmark' Benchmark.bmbm do |x| x.report('fast_fallback: true') do 30.times { Socket.tcp("www.ruby-lang.org", 80) } end x.report('fast_fallback: false') do # Ruby3.3時点と同じ 30.times { Socket.tcp("www.ruby-lang.org", 80, fast_fallback: false) } end end ``` Before: ``` ~/s/build ❯❯❯ ../install/bin/ruby ../ruby/test.rb user system total real fast_fallback: true 0.021315 0.040723 0.062038 ( 0.504866) fast_fallback: false 0.007553 0.026248 0.033801 ( 0.533211) ``` After: ``` ~/s/build ❯❯❯ ../install/bin/ruby ../ruby/test.rb user system total real fast_fallback: true 0.023081 0.040525 0.063606 ( 0.406219) fast_fallback: false 0.007302 0.025515 0.032817 ( 0.418680) ``` -- https://bugs.ruby-lang.org/

1 1

[ruby-core:118483] [Ruby master Bug#20614] Integer#size returns incorrect values on 64-bit Windows
by surusek 22 Jul '24

22 Jul '24

Issue #20614 has been reported by surusek (Łukasz Sur). ---------------------------------------- Bug #20614: Integer#size returns incorrect values on 64-bit Windows https://bugs.ruby-lang.org/issues/20614 * Author: surusek (Łukasz Sur) * Status: Open * ruby -v: ruby 3.4.0dev (2024-07-08T11:00:01Z master 02c4f0c89d [x64-mswin64_140] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- According to the ruby/spec, `0.size` should return size of the machine word in bytes, but on x64-mswin64_140 (both release 3.3.3 and git revision 02c4f0c89d) it doesn't. Following example: ``` ruby a, b = 0.size, [0].pack('J').length puts a, b ``` should print two `8`s, but on x64-mswin64_140, a is `4`. Issue is most likely caused by use of `long` instead of `SIGNED_VALUE` in internal/fixnum.h and `fix_size` function in numeric.c, because on Windows, `long` is always a 32-bit number. -- https://bugs.ruby-lang.org/

6 9

[ruby-core:111448] [Ruby master Bug#19266] URI::Generic should use URI::RFC3986_PARSER instead of URI::DEFAULT_PARSER
by gareth (Gareth Adams) 22 Jul '24

22 Jul '24

Issue #19266 has been reported by gareth (Gareth Adams). ---------------------------------------- Bug #19266: URI::Generic should use URI::RFC3986_PARSER instead of URI::DEFAULT_PARSER https://bugs.ruby-lang.org/issues/19266 * Author: gareth (Gareth Adams) * Status: Open * Priority: Normal * ruby -v: ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [arm64-darwin21] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- In June 2014, [`uri/common` was updated][1] to introduce a RFC3986-compliant parser (`URI::RFC3986_PARSER`) as an alternative to the previous RFC2396 parser, and common methods like `URI()` were updated to use that new parser by default. The only methods in `common` not updated were [`URI.extract` and `URI.regexp`][2] which are marked as obsolete. (The old parser was kept in the `DEFAULT_PARSER` constant despite it not being the default for those methods, presumably for backward compatibility.) However, similar [methods called on `URI::Generic`][3] were never updated to use this new parser. This means that methods like `URI::Generic.build` fail when given input that succeeds normally, and this also affects subclasses like URI::HTTP: ``` $ pry -r uri -r uri/common -r uri/generic [1] pry(main)> URI::Generic.build(host: "underscore_host.example") URI::InvalidComponentError: bad component(expected host component): underscore_host.example from /Users/gareth/.asdf/installs/ruby/3.1.3/lib/ruby/3.1.0/uri/generic.rb:591:in `check_host' [2] pry(main)> URI::HTTP.build(host: "underscore_host.example") URI::InvalidComponentError: bad component(expected host component): underscore_host.example from /Users/gareth/.asdf/installs/ruby/3.1.3/lib/ruby/3.1.0/uri/generic.rb:591:in `check_host' [3] pry(main)> URI("http://underscore_host.example") => #<URI::HTTP http://underscore_host.example> ``` `URI::Generic.new` allows a configurable `parser` positional argument to override the class' default parser, but other factory methods like `.build` don't allow this override. Arguably this doesn't cause problems because at least in the case above, the URI can be built with the polymorphic constructor, but having the option to build URIs from explicit named parts is useful, and leaving the outdated functionality in the `Generic` class is ambiguous. It's possible that the whole Generic class and its subclasses aren't intended to be used directly how I'm intending here, but there's nothing I could see that suggested this is the case. I'm not aware of the entire list of differences between RFC2396 and RFC3986. The relevant difference here is that in RFC2396 an individual segment of a host ([`domainlabel`s][4]) could only be `alphanum | alphanum *( alphanum | "-" ) alphanum`, whereas RFC3986 allows [hostnames][5] to include any of `ALPHA / DIGIT / "-" / "." / "_" / "~"`. It's possible that other differences might cause issues for developers, but since this has gone over 8 years without anyone else caring about this, this is definitely not especially urgent. [1]: https://github.com/ruby/ruby/commit/bb83f32dc3e0424d25fa4e55d8ff32b061320e41 [2]: https://github.com/ruby/ruby/blob/28a17436503c3c4cb7a35b423a894b697cd80da9/… [3]: https://github.com/ruby/ruby/blob/28a17436503c3c4cb7a35b423a894b697cd80da9/… [4]: https://www.rfc-editor.org/rfc/rfc2396#section-3.2.2 [5]: https://www.rfc-editor.org/rfc/rfc3986#page-13 -- https://bugs.ruby-lang.org/

4 8

[ruby-core:118656] [Ruby master Misc#20645] Github release version string changed format
by owlking (Marek Wysinski) 21 Jul '24

21 Jul '24

Issue #20645 has been reported by owlking (Marek Wysinski). ---------------------------------------- Misc #20645: Github release version string changed format https://bugs.ruby-lang.org/issues/20645 * Author: owlking (Marek Wysinski) * Status: Open * Assignee: k0kubun (Takashi Kokubun) ---------------------------------------- https://github.com/ruby/ruby/releases Up to the 3.3.2 release the releases were named with dots and without a v prefix. ruby 3.3.3 is released as "v3.3.3" and 3.3.4 is released as "v3_3_4". I noticed when my automatic ruby update github workflow, based on the github releases api stopped working. Is this an intentional change? Should I update my scripts? -- https://bugs.ruby-lang.org/

2 1