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

[ruby-core:117071] [Ruby master Bug#20327] Time.new behaves differently when passing a zone as timezone object
by davekaro (Dave Kroondyk) 07 Apr '24

07 Apr '24

Issue #20327 has been reported by davekaro (Dave Kroondyk). ---------------------------------------- Bug #20327: Time.new behaves differently when passing a zone as timezone object https://bugs.ruby-lang.org/issues/20327 * Author: davekaro (Dave Kroondyk) * Status: Open * ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [arm64-darwin23] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Time.new with a timezone object for the zone argument produces incorrect utc_offset when passing seconds as a Rational. ``` ruby require "tzinfo" # This correctly outputs 0 as the utc_offset puts Time.new(2024, 1, 1, 23, 59, 59.9r, "UTC").utc_offset # => 0 # Inspecting the time looks correct puts Time.new(2024, 1, 1, 23, 59, 59.9r, "UTC").inspect # => "2024-01-01 23:59:59.9 UTC" # Using a timezone object for the zone, results are different puts Time.new(2024, 1, 1, 23, 59, 59.9r, TZInfo::Timezone.get("Etc/UTC")).utc_offset # => (9/10) # Inspecting the time object reveals the odd offset puts Time.new(2024, 1, 1, 23, 59, 59.9r, TZInfo::Timezone.get("Etc/UTC")).inspect # => "2024-01-01 23:59:59.9 +000001" ``` -- https://bugs.ruby-lang.org/

3 2

[ruby-core:113195] [Ruby master Bug#19592] Unable to statically link a single extension in 3.2.x and >3.1.4
by npic1 (Nat Pic1) 07 Apr '24

07 Apr '24

Issue #19592 has been reported by npic1 (Nat Pic1). ---------------------------------------- Bug #19592: Unable to statically link a single extension in 3.2.x and >3.1.4 https://bugs.ruby-lang.org/issues/19592 * Author: npic1 (Nat Pic1) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Hi, I need to statically link a single extension (not all of them) by adding it to ext/Setup. This worked until version 3.1.4 and 3.2.x. It appears that this change broke it: [https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/79… [https://github.com/ruby/ruby/pull/6756](https://github.com/ruby/ruby/pull/6…. I have attached a script to reproduce the issue. When running the script, `ldd` fails with: ``` ext/extinit.o: in function `Init_ext': extinit.c:(.text+0x10): undefined reference to `ruby_init_ext' ``` ---Files-------------------------------- ruby_static_test.sh (1.57 KB) -- https://bugs.ruby-lang.org/

2 2

[ruby-core:117443] [Ruby master Misc#20410] Backport fix for #19592 to ruby 3.2
by npic1 (Nat Pic1) 05 Apr '24

05 Apr '24

Issue #20410 has been reported by npic1 (Nat Pic1). ---------------------------------------- Misc #20410: Backport fix for #19592 to ruby 3.2 https://bugs.ruby-lang.org/issues/20410 * Author: npic1 (Nat Pic1) * Status: Open ---------------------------------------- Is it possible to backport the fix for this issue in older Ruby versions like 3.2? https://bugs.ruby-lang.org/issues/19592 Thanks -- https://bugs.ruby-lang.org/

2 1

[ruby-core:117408] [Ruby master Misc#20406] Question about Regexp encoding negotiation
by andrykonchin (Andrew Konchin) 04 Apr '24

04 Apr '24

Issue #20406 has been reported by andrykonchin (Andrew Konchin). ---------------------------------------- Misc #20406: Question about Regexp encoding negotiation https://bugs.ruby-lang.org/issues/20406 * Author: andrykonchin (Andrew Konchin) * Status: Open ---------------------------------------- I am wondering what are the rules to calculate Regexp literal encoding in case an encoding modifier is specified. 1. From the documentstion: > By default, a regexp with only US-ASCII characters has US-ASCII encoding: > ... > A regular expression containing non-US-ASCII characters is assumed to use the source encoding. This can be overridden with one of the following modifiers. > //n ... > //u ... > //e ... > //s ... Looking at the following examples I would assume that these rules are followed except one case: ```ruby p /\xc2\xa1/e .encoding # EUC-JP p /#{ }\xc2\xa1/e .encoding # EUC-JP p /a/e .encoding # EUC-JP p /a #{} a/e .encoding # EUC-JP p /#{} a/e .encoding # US-ASCII ``` The last Regexp `/#{} a/e` is supposed to have `EUC-JP` encoding but has `US-ASCII`. So I am wondering what rule is applied in this case. 2. In case of interpolated Regexp with encoding modifier I suppose there is no any encoding negotiation as far as if a Regexp fragment's encoding doesn't match a fixed encoding a SyntaxError is raised. Is this assumption correct? ```ruby /#{ "фв" } a/e # regexp encoding option 'e' differs from source encoding 'UTF-8' (SyntaxError) ``` -- https://bugs.ruby-lang.org/

4 6

[ruby-core:117432] [Ruby master Feature#20408] Add heap_live_slots to GC.stat_heap
by mk 04 Apr '24

04 Apr '24

Issue #20408 has been reported by mk (Matthias Käppler). ---------------------------------------- Feature #20408: Add heap_live_slots to GC.stat_heap https://bugs.ruby-lang.org/issues/20408 * Author: mk (Matthias Käppler) * Status: Open ---------------------------------------- `GC.stat` exposes a `heap_live_slots` metric that returns the number of live objects occupying eden slots. Because the slot size was fixed to `RVALUE_SIZE`, this allowed for some basic approximations of how many bytes were live/in-use (`heap_live_slots * RVALUE_SIZE`). This could furthermore be "embellished" by adding malloc'ed memory for those objects that were larger than a 40B slot (we track this via a custom CRuby patch). However, with the addition of Variable Width Allocations (https://bugs.ruby-lang.org/issues/18239) this does not work anymore because we don't know how `heap_live_slots` distributes over all pools that use different slot sizes. This could be addressed by also adding `heap_live_slots` (and for symmetry: `heap_free_slots`) to `GC.stat_heap`. The sum of all live slots per pool times its respective slot size should equal `GC.stat[:heap_live_slots]`. -- https://bugs.ruby-lang.org/

2 2

[ruby-core:117434] [Ruby master Bug#20409] Missing reporting some invalid breaks
by kddnewton (Kevin Newton) 03 Apr '24

03 Apr '24

Issue #20409 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Bug #20409: Missing reporting some invalid breaks https://bugs.ruby-lang.org/issues/20409 * Author: kddnewton (Kevin Newton) * Status: Open * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- -- https://bugs.ruby-lang.org/

2 3

[ruby-core:117438] [Ruby master Feature#18459] IRB autocomplete dropdown colour options
by hsbt (Hiroshi SHIBATA) 03 Apr '24

03 Apr '24

Issue #18459 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Assigned to Closed https://github.com/ruby/reline/pull/552 fixed this issue. ---------------------------------------- Feature #18459: IRB autocomplete dropdown colour options https://bugs.ruby-lang.org/issues/18459#change-107814 * Author: johansenjaa (Joseph Johansen) * Status: Closed * Assignee: aycabta (aycabta .) ---------------------------------------- It would be great to be able to specify bg/fg colours for the new autocomplete dropdown in irb in ruby 3.1. This could help for accessibility purposes, or for anyone who just wants to make it look more personalised for their terminal 😎 Perhaps irbrc could do the trick? ```ruby IRB.conf[:AUTOCOMPLETE] = { BG_COLOR: 0, FG_COLOR: 15, } ``` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:117425] [Ruby master Feature#4831] Integer#prime_factors
by hsbt (Hiroshi SHIBATA) 03 Apr '24

03 Apr '24

Issue #4831 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Assigned to Closed prime is already extracted from ruby repository to https://github.com/ruby/prime. We should move to its place. ---------------------------------------- Feature #4831: Integer#prime_factors https://bugs.ruby-lang.org/issues/4831#change-107800 * Author: mame (Yusuke Endoh) * Status: Closed * Assignee: yugui (Yuki Sonoda) ---------------------------------------- Hello, lib/prime provides Integer#prime_division, but I always forget the name. I think that #prime_factors is more suitable. I'd like to hear opinions of English natives. What do you think? -- Yusuke Endoh <mame(a)tsg.ne.jp> -- https://bugs.ruby-lang.org/

1 0

[ruby-core:117420] [Ruby master Misc#12751] Incompatibility of Ruby 3
by hsbt (Hiroshi SHIBATA) 03 Apr '24

03 Apr '24

Issue #12751 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Closed Ruby 3 is already released today. ---------------------------------------- Misc #12751: Incompatibility of Ruby 3 https://bugs.ruby-lang.org/issues/12751#change-107795 * Author: naruse (Yui NARUSE) * Status: Closed ---------------------------------------- META ticket for Ruby 3's breakages * Encoding on Windows * [Feature #12654] * [Feature #12650] -- https://bugs.ruby-lang.org/

1 0

[ruby-core:117419] [Ruby master Feature#14125] Readline Module (STDLIB): Add support for ^O emacs keybinding?
by hsbt (Hiroshi SHIBATA) 03 Apr '24

03 Apr '24

Issue #14125 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Closed readline wrapper is extracted to https://github.com/ruby/readline-ext. Can you file your request to https://github.com/ruby/readline-ext ? Or we used reline that is pure ruby altanative of readline today. You may need to file this to https://github.com/ruby/reline. ---------------------------------------- Feature #14125: Readline Module (STDLIB): Add support for ^O emacs keybinding? https://bugs.ruby-lang.org/issues/14125#change-107794 * Author: rlue (Ryan Lue) * Status: Closed ---------------------------------------- The pry gem features a REPL that uses the Readline stdlib module. With the help of this module, pry's REPL supports most emacs-style readline key bindings: * ^P / ^N for navigating up/down the command line history, * ^K for killing text to the end of the line, * ^Y for yanking last-killed text, * ^X^U for undoing, * etc. However, it does NOT support ^O (run command and load next line in history), and I found no reference to the binding in the docs. I can't speak for anyone else, but I'd very much like to see this functionality implemented in the Readline module. -- https://bugs.ruby-lang.org/

1 0