Activity
From 05/02/2025 to 05/08/2025
Today
-
12:53 PM Feature #21311: Namespace on read (revised)
- fxn (Xavier Noria) wrote in #note-44:
> Congrats @tagomoris :).
>
> Would you be open to consider having the perm... -
07:32 AM Feature #21311: Namespace on read (revised)
- Congrats @tagomoris :).
Would you be open to consider having the permanent name of classes and modules be constant... -
05:23 AM Feature #21311: Namespace on read (revised)
- I added committer grants to @tagomoris. Please let me know if you have extra permission or something.
-
04:34 AM Feature #21311: Namespace on read (revised)
- > I nominate @tagomoris (Satoshi Tagomori) for committer.
+1 -
04:25 AM Feature #21311: Namespace on read (revised)
- @tagomoris Can you share your required/optional information to me? see https://github.com/ruby/ruby/wiki/Committer-Ho...
-
04:21 AM Feature #21311: Namespace on read (revised)
- Let's just merge and experiment. We won't know until we actually try it. Also, I nominate @tagomoris for committer.
... - 12:22 PM Revision 5e534849 (git): ZJIT: Temporarily revert path compression
- For reasons I don't understand yet, this causes an issue when trying to
boot yjit-bench. Temporarily revert it. -
09:59 AM Bug #21286: Windows - MSYS2 just updated to GCC 15.1.0, builds failing
- ruby_3_4 merged commit:7e44df91b6d01be68391a029997f5ccdabe80603
-
09:20 AM Revision f3006c26 (git): Add depend files under ext/-test-
-
09:07 AM Feature #21042: Add and expose Thread#memory_allocations memory allocation counters
- only 3 statistics are acceptable.
I don't want to increase more and more measurements from performance perspective. - 09:03 AM Revision a41eed99 (git): [rubygems/rubygems] Update `TarWriter` test to store mtime in a variable
- https://github.com/rubygems/rubygems/commit/0e2cec3fa3
-
09:03 AM Revision 819ecd11 (git): [rubygems/rubygems] Add mtime to Gem::Package::TarWriter#add_file argument
- Since 9e21dd9, Gem::Package::TarWriter#add_file adds the file to
the tar with Gem.source_date_epoch for its mtime.
Th... -
09:03 AM Revision 8685a81e (git): [ruby/strscan] jruby: Check if len++ walked off the end
- (https://github.com/ruby/strscan/pull/153)
Fix https://github.com/ruby/strscan/pull/152
CRuby can walk off the end ... -
09:03 AM Revision 5a0306f9 (git): [ruby/strscan] jruby: Pass end index to byteListToInum
- (https://github.com/ruby/strscan/pull/150)
These parse methods take begin and end indices, not begin and length. A
t... -
09:03 AM Revision 61b6f226 (git): [ruby/json] Constify static data in fpconv.c
- https://github.com/ruby/json/commit/3b605d9b1e
-
09:03 AM Revision 1f2a9dc2 (git): [ruby/psych] Refine Ruby 3.5 Set support.
- Use feature testing to detect native Set,
and don't rely on `Set#to_h` which wasn't intended
as a public method.
htt... -
08:37 AM Misc #21290: Unable to build ruby extension on Fedora 42 due to possible GCC 15 issues
- I also stumbled over this issue and falsely addressed it to mongodb/bson
Here is a Dockerfile which lets you repro... -
03:03 AM Misc #21290: Unable to build ruby extension on Fedora 42 due to possible GCC 15 issues
- Hi,
I am also experiencing a similar issue when trying to install a Ruby gem with C extensions (`blurhash` and `ru... -
07:50 AM Revision 49b4e035 (git): Make test/ruby/test_env.rb#test_delete_if_in_ractor easier to debug
-
07:50 AM Revision 71baa694 (git): variable.c: Fix compilation warnings
- ```
variable.c: In function ‘iterate_over_shapes_with_callback’:
variable.c:2188:1: warning: control reaches end of n... -
05:58 AM Revision cf9046c0 (git): Refactor `id_to_obj_tbl` compaction
- Use `st_foreach_with_replace` rather than to call `st_insert`
from inside `st_foreach`, this saves from having to dis... -
05:58 AM Revision 2d1241ba (git): Get rid of RB_GC_VM_ID_TO_OBJ_TABLE_KEYS
-
05:58 AM Revision f48e45d1 (git): Move `object_id` in object fields.
- And get rid of the `obj_to_id_tbl`
It's no longer needed, the `object_id` is now stored inline
in the object alongsi... -
05:58 AM Revision d34c1505 (git): shape.c: refactor frozen shape to no longer be final
- This opens the door to store more informations in shapes, such
as the `object_id` or object address in case it has be... -
05:58 AM Revision 6c9b3ac2 (git): Refactor OBJ_TOO_COMPLEX_SHAPE_ID to not be referenced outside shape.h
- Also refactor checks for `->type == SHAPE_OBJ_TOO_COMPLEX`.
-
05:58 AM Revision 0ea210d1 (git): Rename `ivptr` -> `fields`, `next_iv_index` -> `next_field_index`
- Ivars will longer be the only thing stored inline
via shapes, so keeping the `iv_index` and `ivptr` names
would be co... -
04:55 AM Bug #21267: respond_to check in Class#allocate is inconsistent
- > Or core types could actually define dup & clone as overridden methods, and not use the alloc function at all and so...
-
04:37 AM Feature #20405: Inline comments
- Using type checkers makes it difficult to write Ruby fluently. To make type checkers work effectively in Ruby, we nee...
-
03:51 AM Feature #21274: Show performance warnings for easily avoidable unnecessary implicit splat allocations
- > The term premature optimization typically refers to cases where you optimize, and later, the optimization results i...
-
03:25 AM Feature #21274: Show performance warnings for easily avoidable unnecessary implicit splat allocations
- Dan0042 (Daniel DeLorme) wrote in #note-2:
> I appreciate the effort here, but I wonder if this might be a case of p... -
03:06 AM Feature #21274: Show performance warnings for easily avoidable unnecessary implicit splat allocations
- I appreciate the effort here, but I wonder if this might be a case of premature micro-optimization. Was there a measu...
-
03:34 AM Revision 4e30b77b (git): Added depend file for test/-ext-/econv/test_append.rb
- https://github.com/ruby/ruby/commit/ce51ef30df5bf07ec3881a377f0011b8f20ec507 broke
ext/-test-/econv/append.o. We shou... -
01:59 AM Feature #21279: Bare "rescue" should not rescue NameError
- byroot (Jean Boussier) wrote in #note-5:
> 99% of the time, when I use a bare `rescue` it's because I'll call `raise... -
01:30 AM Feature #15408: Deprecate ObjectSpace._id2ref
- The original reason to deprecate `_id2ref` is no longer relevant now that `object_id` is a monotonically-increasing I...
05/07/2025
-
05:29 PM Feature #21311: Namespace on read (revised)
- Eregon (Benoit Daloze) wrote in #note-12:
> Unless they truly need to communication at all between namespaces, but t... -
05:20 PM Feature #21311: Namespace on read (revised)
- Basically, I believe the idea is to have isolated execution contexts without forking, but is hard to achieve that by ...
-
05:18 PM Feature #21311: Namespace on read (revised)
- tagomoris (Satoshi Tagomori) wrote in #note-28:
> Mounting server-less applications (run on AWS Lambda, separated on... -
05:09 PM Feature #21311: Namespace on read (revised)
- tagomoris (Satoshi Tagomori) wrote:
> Root namespace is a unique namespace to be defined when a Ruby process starts.... -
05:07 PM Feature #21311: Namespace on read (revised)
- Aaron that is a concern I have also in mind that I have not expressed yer.
The current proposal allows access to t... -
05:01 PM Feature #21311: Namespace on read (revised)
- Eregon (Benoit Daloze) wrote in #note-12:
> * Any user-defined class instance won't be `is_a?` in another namespace ... -
04:36 PM Feature #21311: Namespace on read (revised)
- Dan0042 (Daniel DeLorme) wrote in #note-19:
> I'm not sure if this can be achieved with TruffleRuby sub-interpreters... -
02:57 PM Feature #21311: Namespace on read (revised)
- @tagomoris thanks for your replies, even more with such a busy thread :). Let me followup:
> There should be no need... -
02:24 PM Feature #21311: Namespace on read (revised)
- byroot (Jean Boussier) wrote in #note-24:
> But I'd like to hear about common green path, day to day, use cases, not ... -
02:09 PM Feature #21311: Namespace on read (revised)
- Thank you for expanding on the motivation, the design makes more sense to me now.
I'm still not convinced the trad... -
02:04 PM Feature #21311: Namespace on read (revised)
- @fxn
> So, I guess spawning does not create hierarchy. A namespace may not have a pointer to the namespace where i... -
01:48 PM Feature #21311: Namespace on read (revised)
- I'm sorry that I skipped to make effort to describe the motivation and copied the motivation section from the past ti...
-
07:08 AM Feature #21311: Namespace on read (revised)
- I have compiled the branch and I am playing around a bit with `miniruby` to test my understanding of the feature.
So... -
02:19 AM Feature #21311: Namespace on read (revised)
- FYI: you can try namespace PR on https://ruby.github.io/play-ruby/?run=14855772787&options=%7B%22arguments%22%3A%5B%5...
-
05:09 PM Feature #21254 (Closed): Inlining Class#new
- mame (Yusuke Endoh) wrote in #note-10:
> @tenderlovemaking Can we close this?
Yes, sorry. I thought I had closed ... -
06:37 AM Feature #21254: Inlining Class#new
- Note: https://github.com/ruby/ruby/pull/13080 has been merged.
-
06:36 AM Feature #21254: Inlining Class#new
- @tenderlovemaking Can we close this?
-
05:04 PM Revision 7e44df91 (git): Fix C23 (GCC 15) WIN32 compatibility for rb_define_* functions
- Backport [Bug #21286]
-
03:47 PM Revision 3e94b5f9 (git): Remove dependence on internal/hash.h for default GC
-
06:07 AM Bug #18878 (Assigned): parse.y: Foo::Bar {} is inconsistently rejected
-
05:01 AM Misc #21281: DevMeeting-2025-05-08
- * [Feature #21258] Retire CGI library from Ruby 3.5
* Can I remove CGI library without `CGI::Util` ?
* What's the...
05/06/2025
-
11:50 PM Bug #21312 (Assigned): ruby 3.5-dev installs a gemspec for rdoc that misses dependencies
-
05:46 PM Bug #21312 (Assigned): ruby 3.5-dev installs a gemspec for rdoc that misses dependencies
- Similarly to https://bugs.ruby-lang.org/issues/20581, installing ruby 3.5-dev installs a gemspec for rdoc that it's m...
-
10:35 PM Revision 4aac1506 (git): Skip an unstable Ractor test
-
10:34 PM Revision 7afa08ce (git): YJIT: End the block after OPTIMIZE_METHOD_TYPE_CALL
-
10:32 PM Bug #21310 (Feedback): YJIT optimization causes incorrect is_a? method evaluation
- I think it's most likely fixed by https://github.com/ruby/ruby/pull/13245. It's going to be shipped in the next relea...
-
01:08 AM Bug #21310 (Feedback): YJIT optimization causes incorrect is_a? method evaluation
- Our Rails application contains code like the following:
```ruby
result = a_proc.call
if result.is_a?(Result) &... -
10:32 PM Revision d6d63b27 (git): Enabled debug mode for CodeQL
-
08:00 PM Feature #21311: Namespace on read (revised)
- Agreed on all points. I have little concept of the complexity of the implementation, and defer to you on that. I th...
-
07:03 PM Feature #21311: Namespace on read (revised)
- peter.boling (Peter Boling) wrote in #note-23:
> One use case for this is to benchmark libraries that do the same ... -
06:41 PM Feature #21311: Namespace on read (revised)
- byroot (Jean Boussier) wrote in #note-13:
> > Avoiding name conflicts between libraries: Applications can require two... -
06:01 PM Feature #21311: Namespace on read (revised)
- Dan0042 (Daniel DeLorme) wrote in #note-19:
> It's not about "working around" libraries. It's about loading entirely... -
04:47 PM Feature #21311: Namespace on read (revised)
- If my interpretation is correct, the entry point of a library will be executed as many times as user namespaces requi...
-
04:38 PM Feature #21311: Namespace on read (revised)
- My interpretation of the vocabulary is as following:
1. The interpreter boots in a `root` namespace.
1. The "state" ... -
03:13 PM Feature #21311: Namespace on read (revised)
- byroot (Jean Boussier) wrote in #note-13:
> I personally see namespaces as a feature libraries can use to write more... -
02:59 PM Feature #21311: Namespace on read (revised)
- > The main and user namespaces are independent
@eregon the description says
> User namespace is a namespace to ... -
12:11 PM Feature #21311: Namespace on read (revised)
- @byroot makes a good point about use cases, I share the same concerns (and already did in https://bugs.ruby-lang.org/...
-
12:01 PM Feature #21311: Namespace on read (revised)
- Has the performance of Namespace been evaluated?
I would assume getting the current namespace to execute methods/pro... -
11:56 AM Feature #21311: Namespace on read (revised)
- (from description)
> There is no way to access App in the main namespace from the code in the different namespace ns... -
11:55 AM Feature #21311: Namespace on read (revised)
- While I believe namespaces would be a good addition to Ruby, I'm not convinced this particular implementation of
nam... -
11:52 AM Feature #21311: Namespace on read (revised)
- I think this addresses https://bugs.ruby-lang.org/issues/19744#note-74 by having a CoW copy of all builtin classes/mo...
-
11:38 AM Feature #21311: Namespace on read (revised)
- @fxn The main and user namespaces are independent, though the main namespace can refer to user namespace via `ns::Som...
-
10:18 AM Feature #21311: Namespace on read (revised)
- > having a block parameter on Namespace.new could provide similar UX without changing syntax.
That wouldn't handle... -
10:17 AM Feature #21311: Namespace on read (revised)
- > any user-defined classes/modules are not defined in the root namespace.
Ah, that is key.
So, what happens in ... -
10:01 AM Feature #21311: Namespace on read (revised)
- fxn (Xavier Noria) wrote in #note-6:
> In Ruby, objects are stored in constants. Conceptually, a constant `X` storin... -
09:22 AM Feature #21311: Namespace on read (revised)
- Thanks @tagomoris.
> Conceptually, yes. Definitions are deeply cloned. But objects (stored on constants, etc) will n... -
08:00 AM Feature #21311: Namespace on read (revised)
- fxn (Xavier Noria) wrote in #note-2:
> A few quick questions:
>
> Assuming a normal execution context, nesting at... -
07:46 AM Feature #21311: Namespace on read (revised)
- @baweaver I don't have strong opinion about adding `namespace` keyword, but having a block parameter on `Namespace.ne...
-
06:24 AM Feature #21311: Namespace on read (revised)
- A few quick questions:
Assuming a normal execution context, nesting at the top level of a file is empty. Would it be... -
05:46 AM Feature #21311: Namespace on read (revised)
- As a proof of concept this is a very valuable idea, and will give users a chance to experiment with it.
I wonder a... -
05:16 AM Feature #21311 (Open): Namespace on read (revised)
- This replaces #19744
## Concept
This proposes a new feature to define virtual top-level namespaces in Ruby. Th... -
07:45 PM Bug #21313 (Open): `it` in rescue/ensure on prism
- ```ruby
1.times do
raise
rescue
p it
#=> prism: false
#=> parse.y: 0
end
```
`it` should return 0,... -
05:13 PM Revision cb772247 (git): Improve correctness contention for allocated object counts
- Currently the count of allocated object for a heap is incremented
without regards to parallelism which leads to incor... - 03:11 PM Revision 925da368 (git): Parse topn, opt_length, opt_size into HIR
-
11:18 AM Feature #21309: Can Thread::Mutex be Ractor shareable?
- > Now, more generally, if we got some shareable mutable state, then we'd need a shareable mutex. I just haven't yet e...
-
10:14 AM Feature #21309: Can Thread::Mutex be Ractor shareable?
- I'm not sure I see the use case for `Mutex` to be shareable, at least in this specific scenario.
To take the `Time... -
08:19 AM Feature #21309: Can Thread::Mutex be Ractor shareable?
- > At least for Queue it's not that simple, because it contains objects
Indeed, you're right about Queue. I overloo... -
09:19 AM Feature #21308: Replacing the Float#to_s (dtoa.c) implementation with a modern algorithm
- The interface of `fpconv_dtoa()` looks quite different from `dtoa()` in missing/dtoa.c.
Rather `grisu2()` itself is ... -
05:23 AM Feature #19744 (Closed): Namespace on read
-
05:19 AM Feature #19744: Namespace on read
- This is replaced by #21311.
Could someone close this? -
05:06 AM Revision 1c68aae9 (git): Check LoadError first
- The message from dlerror is not our concern.
-
05:06 AM Revision 54950b1f (git): Added assertion strings with Xcode 16.3 beta
-
03:11 AM Bug #21286: Windows - MSYS2 just updated to GCC 15.1.0, builds failing
- ruby_3_3 commit:ffd469bd6d06df10057325a5b8c773fca009af8d merged revision(s) commit:719486a642f0e282b02b958069b8b39b85...
-
02:29 AM Revision ffd469bd (git): merge revision(s) 719486a642f0e282b02b958069b8b39b85b3aa1e: [Backport #21286]
- Fix C23 (GCC 15) WIN32 compatibility for rb_define_* functions
Fixes [Bug #21286]
05/05/2025
-
09:26 PM Bug #21030: Bug: #step with Range<ActiveSupport::Duration> behavior broken on Ruby 3.4.1
- I also verified the fix in 3.4.3 in my app. The behavior is correct.
-
08:09 PM Bug #21030: Bug: #step with Range<ActiveSupport::Duration> behavior broken on Ruby 3.4.1
- @jamesst20 https://github.com/ruby/ruby/commit/6d2c7d4304bbf8450d31b624f5dc40a92e44f00b is in 3.4.3 though.
And I don... -
06:44 PM Bug #21030: Bug: #step with Range<ActiveSupport::Duration> behavior broken on Ruby 3.4.1
- jamesst20 (James St-Pierre) wrote in #note-8:
> According to the changelogs for v3.4.2, this wasn't included?
>
>... -
08:35 PM Revision cbf9c088 (git): YJIT: End the block after OPTIMIZE_METHOD_TYPE_CALL (#13245)
-
08:04 PM Feature #21309: Can Thread::Mutex be Ractor shareable?
- At least for Queue it's not that simple, because it contains objects, and the invariants of Ractor (without which it ...
-
04:46 PM Feature #21309 (Open): Can Thread::Mutex be Ractor shareable?
- ## Background
Keeping a `Mutex` object in a constant or a class instance variable is a common pattern seen in code... -
04:04 PM Revision 4621feb6 (git): ZJIT: Use 2024 edition for rustc-only release builds
-
01:55 PM Revision e042e106 (git): vm_dump.c: avoid `USE_MN_THREADS` is not defined warning
-
01:34 PM Revision 3a2e56e6 (git): Fix `USE_MN_THREADS=0` builds on macOS
- This was recently broken.
-
12:44 PM Revision a3af4e90 (git): Make rb_shape.capacity an `attr_index_t`
-
12:44 PM Revision bbea71fa (git): variable.c: Fix too_complex shape initialization
- `SHAPE_OBJ_TOO_COMPLEX` is a `shape_type` not a `shape_id_t`.
-
12:44 PM Revision 53ae5580 (git): Improve style consistency of `rb_shape_t *`
-
10:20 AM Bug #21304 (Closed): heap-use-after-free of Array#hash via mutating hash method
- Applied in changeset commit:git|ce8f7da49e2fea995993b49aa7a26f7640c2e258.
----------
[Bug #21304] Reload length and ... -
10:20 AM Revision 5b1a61e2 (git): [ruby/digest] stringop-overread warning is since GCC 11
- https://github.com/ruby/digest/commit/d16853fe8c
-
09:40 AM Feature #21308 (Open): Replacing the Float#to_s (dtoa.c) implementation with a modern algorithm
- This is a feature request to replace Ruby's `Float#to_s` implementation with a modern high-performance float-to-strin...
-
09:25 AM Revision bbf1130f (git): Add `RBIMPL_ATTR_NONSTRING_ARRAY()` macro for GCC 15
-
05:27 AM Bug #21298: `ObjectSpace.allocation_class_path` returns inconsistent results depending on `TracePoint` state
- > Would it be possible for power_assert to avoid depending on Class#new being present in the stack trace?
I update... -
12:46 AM Revision ce51ef30 (git): Save one VALUE per embedded RTypedData
- This halves the amount of memory used for embedded RTypedData if they
are one VALUE (8 bytes on 64-bit platforms) ove...
05/04/2025
-
09:14 PM Revision 35918df7 (git): [DOC] Tweaks for String#+
-
09:14 PM Revision d2de5979 (git): [DOC] Tweaks for String#*
-
09:13 PM Revision d71e1714 (git): [DOC] Tweaks for String#%
-
01:17 PM Misc #21290: Unable to build ruby extension on Fedora 42 due to possible GCC 15 issues
- I confirm I have the same problem on arch. With multiple ruby version (3.2, 3.3, 3.4). Example of gems failing are `j...
-
07:42 AM Misc #21290: Unable to build ruby extension on Fedora 42 due to possible GCC 15 issues
- Thanks for the heads-up about using `append_flags`. I used it to fix the issue for the ed25519 gem and a new version ...
-
12:40 PM Revision ce8f7da4 (git): [Bug #21304] Reload length and pointer after `#hash` method
- The receiver can be modified during the method calls.
-
12:38 PM Bug #21267: respond_to check in Class#allocate is inconsistent
- I think it makes sense to replace or remove that "incorrect" check given it doesn't apply to `new`.
The proper fix s... -
01:19 AM Bug #21267: respond_to check in Class#allocate is inconsistent
- At RubyKaigi @byroot and I looked at this and came up with a more efficient and resilient way to do the check (https:...
-
10:43 AM Bug #21302: Remove or Fix Set#to_h
- I agree to remove it.
-
02:05 AM Bug #21301: Invalid Dates Accepted When Using "UTC" in Time.new
- Ah yeah, rolling over seconds seems trickier. I think the time with the offset doesn't have to deal with all that bec...
-
01:26 AM Misc #21281: DevMeeting-2025-05-08
- * [Feature #21267] `respond_to` check in `Class#allocate` is inconsistent
* `Class#allocate` does a slow `respond_...
05/03/2025
-
07:11 PM Bug #21306 (Closed): heap-use-after-free in set initialization via clearing the array while it’s being iterated
- Applied in changeset commit:git|21035c826db5933cf836a4a12fb74b696a76b255.
----------
Handle mutating of array passed... -
06:23 PM Bug #21306: heap-use-after-free in set initialization via clearing the array while it’s being iterated
- Potential fix in https://github.com/ruby/ruby/pull/13253
I'm not sure ASAN is supported on OpenBSD, so I'm not sur... -
01:26 PM Bug #21306 (Closed): heap-use-after-free in set initialization via clearing the array while it’s being iterated
- Hi, we found a heap-use-after-free in set initialization
via clearing the array while it’s being iterated. Here is t... -
07:11 PM Bug #21305 (Closed): heap-use-after-free of set#merge via mutating hash method
- Applied in changeset commit:git|be665cf855d7b35ce166ea1137d4f8d0cac1010b.
----------
Handle mutation of array being ... -
06:23 PM Bug #21305: heap-use-after-free of set#merge via mutating hash method
- Potential fix in https://github.com/ruby/ruby/pull/13253
I'm not sure ASAN is supported on OpenBSD, so I'm not sur... -
01:19 PM Bug #21305 (Closed): heap-use-after-free of set#merge via mutating hash method
- Hi, we found a heap-use-after-free of set#merge via mutating hash method. Here
is the PoC.
```
class C
def ... -
07:10 PM Revision 21035c82 (git): Handle mutating of array passed to Set.new during iteration
- This avoids a heap-use-after-free.
Fixes [Bug #21306] -
07:10 PM Revision be665cf8 (git): Handle mutation of array being merged into set
- Check length of array during every iteration, as a #hash method
could truncate the array, resulting in heap-use-after... -
06:39 PM Bug #21302: Remove or Fix Set#to_h
- I think you can just remove it. I used it in Pysch because it was there, if it wasn't intended to be added, just remo...
-
07:35 AM Bug #21302 (Open): Remove or Fix Set#to_h
- When backwards-compatible marshalling support for Set was added in commit:926411171d296859839745a536aa86bc1e18aa76, S...
-
06:25 PM Misc #21281: DevMeeting-2025-05-08
- * [Feature #21307] A way to strictly validate time input (mame)
* I want to confirm that the current tolerant behav... -
07:43 AM Misc #21281: DevMeeting-2025-05-08
- * [Feature #21274] Show performance warnings for easily avoidable unnecessary implicit splat allocations (jeremyevans...
-
06:17 PM Feature #21307 (Open): A way to strictly validate time input
- Currently, `Time.new` sometimes silently rolls over invalid date/time values:
```ruby
Time.new(2025, 2, 29, 0, 0,... -
05:22 PM Bug #21304: heap-use-after-free of Array#hash via mutating hash method
- Thanks for the clear bug report! https://github.com/ruby/ruby/pull/13250
-
01:14 PM Bug #21304 (Closed): heap-use-after-free of Array#hash via mutating hash method
- Hi, we found a heap-use-after-free of Array#hash via mutating hash method. Here
is the PoC.
```
class C
def... -
05:20 PM Bug #21303 (Closed): heap-buffer-overflow of Array#difference via mutating hash method
- Applied in changeset commit:git|f3246ccebb0ccb8667fc6f143e69ecc2a9e3fb3c.
----------
Fix an ASAN error in Array#diff... -
04:48 PM Bug #21303: heap-buffer-overflow of Array#difference via mutating hash method
- Thanks! I created a PR: https://github.com/ruby/ruby/pull/13249
-
12:55 PM Bug #21303 (Closed): heap-buffer-overflow of Array#difference via mutating hash method
- Hi, we found a heap-buffer-overflow of Array#difference via mutating hash
method. Here is the PoC.
```
class C
... -
05:20 PM Revision f3246cce (git): Fix an ASAN error in Array#difference
- [Bug #21303]
-
04:34 PM Bug #21301: Invalid Dates Accepted When Using "UTC" in Time.new
- Thanks. Actually, the same issue also occurs with a value of 60 for seconds:
```ruby
Time.new(2025, 1, 1, 0, 0, 6... -
03:35 AM Bug #21301: Invalid Dates Accepted When Using "UTC" in Time.new
- Possible fix: https://github.com/ruby/ruby/pull/13246
- 12:39 PM Revision 2be117a9 (git): Fix `heap-use-after-free` in `free_fast_fallback_getaddrinfo_entry` (#13231)
- This change addresses the following ASAN error:
```
==36597==ERROR: AddressSanitizer: heap-use-after-free on address... -
06:58 AM Bug #21280: StringIO#set_encoding warns when backed by chilled string literal
- It seems like most developers are against treating chilled strings differently than unfrozen strings in this case. I...
05/02/2025
-
09:32 PM Bug #21301 (Open): Invalid Dates Accepted When Using "UTC" in Time.new
- 2025-04-31 does not exist, but, when creating a time object with the "UTC" zone, the value is accepted without error:...
-
09:28 PM Revision 36c64b3b (git): Also prefer FL_TEST_RAW in gc.c
- Similar to 4a040eeb0d880b67a5005cce382122fd5b629b99, I noticed the test
for FL_FINALIZE checking FL_ABLE in a profile... - 08:01 PM Revision 23000c73 (git): ZJIT: Parse opt_newarray_send into HIR (#13242)
-
05:36 PM Revision 186022d1 (git): wasm: increase the default Asyncify buffer size
- We will need more Asyncify space for the upcoming namespace changes
as it will introduce more local variables and con... -
05:18 PM Bug #21286: Windows - MSYS2 just updated to GCC 15.1.0, builds failing
- Please kindly backport this to all actively maintained versions (3.2, 3.3, 3.4). Since MSYS2 gcc is installed indepen...
-
04:02 PM Revision ac311437 (git): [Backport 3.4] Fix C level backtraces for USE_ELF
- [Backport #21289]
-
02:47 PM Revision 33909a1c (git): YJIT: ZJIT: Share identical glue functions
- Working towards having YJIT and ZJIT in the same build, we need to
deduplicate some glue code that would otherwise ca... -
02:47 PM Revision aafd1061 (git): Add an include guard for insns_info.inc
- The JIT bindgens need this.
-
12:06 PM Revision dd0e0eb4 (git): Delete always true assert [ci skip]
-
09:46 AM Revision 85198262 (git): [ruby/digest] Suppress false stringop-overread warning
- https://github.com/ruby/digest/commit/0df846e8c1
-
09:46 AM Revision 277bcb71 (git): [ruby/digest] Move macros for warnings to defs.h
- https://github.com/ruby/digest/commit/70a805b872
-
09:38 AM Feature #21300: Suggestion: Method for Array truncation
- Using `ary.size =` feels unidiomatic Ruby to me, it feels very low level and not very expressive about the intent (e....
-
08:31 AM Feature #21300 (Open): Suggestion: Method for Array truncation
- `#pop(n)` and `#slice!(...)` can be used for truncation, but they both allocate a new array for the deleted elements ...
-
09:20 AM Revision ba6a36e6 (git): [ruby/digest] Fix `--without-common-digest` option
- In `digest_conf`, "no implicit conversion of false into String"
TypeError is raised.
https://github.com/ruby/digest/... -
06:27 AM Revision 430789de (git): [ruby/psych] Ensure to remove the test constants
- https://github.com/ruby/psych/commit/dd3685aa67
- 01:40 AM Revision d2a0e98c (git): Update default gems list at 0f066269150375982712bd4a918438 [ci skip]
-
01:11 AM Revision 0f066269 (git): Bump up strscan version to 3.1.5.dev
- 12:52 AM Revision af6d6b64 (git): [ruby/strscan] named_captures: fix incompatibility with
- MatchData#named_captures
(https://github.com/ruby/strscan/pull/146)
Fix https://github.com/ruby/strscan/pull/145
`M... - 12:49 AM Revision a1e627b7 (git): [ruby/psych] Use `rb_struct_initialize` to initialize Data
- https://github.com/ruby/psych/commit/3573fb356e
- 12:49 AM Revision 5d070837 (git): [rubygems/rubygems] Smoother authentication experience
- Copying the URL is painful here because the URL is embedded within a paragraph of text. I presume we don't want to au...
-
12:49 AM Revision 69bb2b3b (git): Set is migrated to Core class
-
12:14 AM Bug #21298: `ObjectSpace.allocation_class_path` returns inconsistent results depending on `TracePoint` state
- @tenderlovemaking Oh thank you!
@ktsj Would it be possible for `power_assert` to avoid depending on `Class#new` be...
Also available in: Atom