Activity
From 05/07/2025 to 05/13/2025
05/13/2025
-
11:54 PM Revision 1d3221ad (git): [ruby/erb] Give up on using resolve_feature_path
- Apparently `$LOAD_PATH.resolve_feature_path('erb/escape')` returns true
for miniruby but `require 'erb/escape'` fails on it.
I still don't want to check it and rescue LoadError at the same time
because the code looks too complicated. Le... -
11:41 PM Bug #21334: Namespaces and object reference sharing
- I have spent countless hours of my free time on namespaces in the last days. I experimented with the feature again tonight, and wrote this ticket with care, looking for edge cases, and presenting them, past midnight.
While rejecting on ... -
- > If you call something like ref.http_client.fetch, the method fetch is executed in the context of the namespace where http_client lives. That's the namespace where blank? is defined. So in that case, the call should work.
`blank?` was ... -
11:01 PM Bug #21334 (Rejected): Namespaces and object reference sharing
- I've lost count of how many times I've said this, but here it is again:
**You must provide reproducible code, your expectation, and actual results.**
The current implementation of namespaces is incomplete, and code using real-world... -
- > Maybe redefine communication across namespaces in a very restrictive way that make these issues by design
Maybe redefine communication across namespaces in a very restrictive way that **prevents** these issues by design -
- # Implications related to builtin classes and modules
As we know, when a namespace is created, builtin classes in the namespace are as in the root one. This applies to all references to them, explicit or implicit.
This is at the co... -
- (https://github.com/ruby/erb/pull/61)"
This reverts commit https://github.com/ruby/erb/commit/1c9200aab071.
Now that we've bumped BASERUBY, we shouldn't need to rescue the
LoadError.
https://github.com/ruby/erb/commit/846b20fe0e -
10:51 PM Feature #21335 (Open): Namespaces should be present in the backtrace
- Namespaces can call in to other name spaces. I think it might be helpful if namespace information is in the backtrace.
For example:
```ruby
File.binwrite "foo.rb", <<-eorb
class Foo
def self.test(ns1, ns2, count)
if count... -
- Eregon (Benoit Daloze) wrote in #note-82:
> @matz What real-world use cases do you see for Namespace?
One thing I can think of is running multiple Rails applications in one process. Right now Rails applications are basically singlet... -
11:28 AM Feature #21311: Namespace on read (revised)
- mame (Yusuke Endoh) wrote in #note-51:
> This feature proposal is quite exceptional. Because this is a feature strongly driven by @matz himself, and Ruby is matz's language.
> ...
I took some time before replying here to try to find the ... -
06:13 AM Feature #21311: Namespace on read (revised)
- > (In fact, the overhead appears to be only about 5%.)
That's when namespaces aren't used. Since creating a namespace start some sort of de-optimization phase, I assume the impact is way worse with `RUBY_NAMESPACE=1`, but I couldn't ... -
- jhawthorn (John Hawthorn) wrote in #note-79:
> Sorry, I didn't get a chance to review this before it was merged. I really don't think adding this level of indirection to RCLASS_EXT access and similar is a good idea.
Since I was the o... -
- This ticket was kind of oriented to docs.
I believe the emphasis has to be different and have created https://bugs.ruby-lang.org/issues/21334.
This one can be close if you will. -
- So `#update` with block isn't considered iteration, so it doesn't increase the `iterlevel` hence `#rehash` is mistakenly allowed.
At first sight the fix is to treat `#update` like an iteration when yielding. -
- ```ruby
$a = (1..1337).to_h { |k| [k, k] }
$b = (1..1337).to_h { |k| [k, k * 2] }
$a.update($b) { |k, o, n|
$a.rehash
}
```
Seem to do the trick. -
- The reproduction script seem missing something? `$b` is `nil` here so the script simply fail.
-
12:19 PM Bug #21333 (Closed): heap-use-after-free caused by rehash during update
- Hi, we found a heap-use-after-free caused by rehash during update
```
$a = (1..1337).to_h { |k| [k, k] }
$a.update($b) { |k, o, n|
$a.rehash
}
```
```
$ git log | head -n4
commit a6435befa76c2ae0525147f934bd9cd1914ffb8a
... -
-
-
- Applied in changeset commit:git|1ee4b43a56e9539d3b09c08114c59cb49857b956.
----------
Set#merge: raise if called during iteration
[Bug #21332] -
- `Set#merge` is missing a check for iteration: https://github.com/ruby/ruby/pull/13322
-
- Hi, we found a heap-use-after-free caused by mutating the set.
hash() returning 0 is important to create the collision and then trigger eql?
```
$flag = false
$c = 0
class C
def hash
return 0
end
def eq... -
- [Bug #21332]
- 08:23 PM Revision 1d4822a1 (git): Get ractor message passing working with > 1 thread sending/receiving values in same ractor
- Rework ractors so that any ractor action (Ractor.receive, Ractor#send, Ractor.yield, Ractor#take,
Ractor.select) will operate on the thread that called the action. It will put that thread to sleep if
it's a blocking function and it needs... -
- It currently fails like: Can't find 'action.yml'
-
- https://github.com/ruby/erb/commit/c2d1f82817
-
- (https://github.com/ruby/erb/pull/61)"
This reverts commit https://github.com/ruby/erb/commit/1c393aa738f3.
https://github.com/ruby/erb/commit/1c9200aab0 - 06:10 PM Revision f82dce14 (git): Update default gems list at 9db0704e67c8af3b47429e28e1da5e [ci skip]
-
- https://github.com/ruby/erb/commit/08b544cdb8
-
- Even cgi.gem publicly defines CGI::VERSION today. It's just weird that
ERB::VERSION is kept private at this point.
https://github.com/ruby/erb/commit/46801cbd47 -
06:02 PM Bug #21327: Windows builds seem broken after clock_gettime changes?
- I just tested this with the ruby_3_4 branch. It's failing with:
```
../ruby/win32/win32.c:4795:1: error: redefinition of 'clock_gettime'
4795 | clock_gettime(clockid_t clock_id, struct timespec *sp)
| ^~~~~~~~~~~~~
In file i... -
12:59 AM Bug #21327: Windows builds seem broken after clock_gettime changes?
- It's fixed at https://github.com/ruby/ruby/pull/13302
But cross build is still broken.
* https://rubyci.s3.amazonaws.com/crossruby/crossruby-master-mingw32/log/20250513T000922Z.fail.html.gz
* https://rubyci.s3.amazonaws.com/crossr... - 06:00 PM Revision 4a9d46ce (git): [ruby/erb] Refactor the logic of require 'erb/escape'
- (https://github.com/ruby/erb/pull/61)
https://github.com/ruby/erb/commit/1c393aa738 - 05:50 PM Revision 735f2838 (git): [ruby/erb] Support all cgi.gem versions
- (https://github.com/ruby/erb/pull/60)
https://github.com/ruby/erb/commit/de9bb8c3cc -
- RUBY_FL_USER3
(https://github.com/ruby/stringio/pull/133)
This way when someone removes these flags from Ruby or update them,
they'll find this reference when greping.
Followup: https://github.com/ruby/stringio/pull/128
https://github... -
05:14 PM Revision 96b823a2 (git): [DOC] Tweaks for String#<=>
-
04:37 PM Bug #21331 (Closed): heap-use-after-free caused by rehash during transform_values!
- Applied in changeset commit:git|bb180b87b43c45e17ff49735a26d7a188d5c8396.
----------
[Bug #21331] Prohibit modification during stlike loop -
- https://github.com/ruby/ruby/pull/13317
-
- Hi, we found a heap-use-after-free caused by rehash during transform_values!.
```
$a = (1..1337).to_h { |k| [k, k] }
$a.transform_values! { |v|
$a.rehash
v * 2
}
```
```
$ git log | head -n4
commit a6435befa76c2ae05... -
- I was able to reproduce the bug, and rebasing @luke-gru 's patch does indeed fix the hang (I reduced 100M to 10M though cause it's very long otherwise).
@jhawthorn or @tenderlovemaking could you review the PR? The patch make sense to ... -
02:42 PM Bug #17624: Ractor.receive is not thread-safe
- Related to https://bugs.ruby-lang.org/issues/21037
-
- I was able to reproduce this on 3.3, but not on 3.4 not master. So I'll assume it was fixed and close.
-
- 02:16 PM Revision 1e2a67e1 (git): Fix typo in `NEWS.md`.
-
01:54 PM Bug #21166: Fiber Scheduler is unable to be interrupted by `IO#close`.
- I've renamed `rb_thread_io_interruptible_operation` to `rb_thread_io_blocking_operation` which better suits the naming convention internally.
-
- https://github.com/ruby/ruby/pull/13127 has been merged, allowing us to move forward with this feature.
-
- The `includer` field is only used for `T_ICLASS`, so by moving
it into the existing union we can save one `VALUE` per class
and module. -
12:00 PM Bug #21330: Namespace: Class and Module frozen status is not namespaced
- The frozen flag is what I missed. I think we should move the flag to `rb_classext_t`.
-
- ```ruby
File.write("/tmp/test.rb", <<~'RUBY')
Hash.freeze
RUBY
ns = Namespace.new
ns.require("/tmp/test.rb")
class Hash
def monkey_patch
end
end
```
Expected behavior:
Since the monkey patch is in a different na... -
11:52 AM Bug #21316: Namespaces leak with permanent names
- @Eregon It has already been fixed. Thank you.
-
- @make_now_just In the first two cases, it should be `.dump_in_ns` not `.dump`
-
- I found an issue on `Marshal` and `Namespace` maybe related to this ticket.
When dumping an object defined in a namespace using Marshal, the result will vary depending on whether the namespace is held as a variable or constant, and whet... -
- byroot (Jean Boussier) wrote in #note-1:
> ### Half-way solution
> ...
I think this would be a pretty good solution actually, it seems very unlikely to have class names which can't be encoded in UTF-8. -
- In my opinion, we need to introduce a new format for dumping classes/modules correctly.
Marshal uses `c` and `m` (`TYPE_CLASS` and `TYPE_MODULE`) as format prefixes currently, so the format is the following:
```
| 1 byte | ... | ... -
- Loading RubyGems creates more constants than just `Gem`:
```
$ ruby -v --disable-gems -e 'a=Object.constants; require "rubygems"; b=Object.constants; p b-a'
ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]
[:Monitor,... -
06:47 AM Bug #21324: Namespace loads RubyGems in root Namespace but it should not
- I've identified the issue and prepared a fix.
The problem is that RubyGems is being loaded into the root namespace during Ruby's boot process, and then all user namespaces inherit this same Gem constant through the Copy-on-Write mecha... -
- Applied in changeset commit:git|c941fced211c7472d6a61e7469b70282ac506ea6.
----------
Throw RuntimeError if getting/setting ractor local storage for non-main ractor
[Bug #19367] -
- [Bug #19367]
-
11:14 AM Bug #21329: `date_core.so` is broken with the recent MSYS2 update
- Some debugging happening at https://github.com/ruby/date/pull/125 already! Should this be moved to the date repo, by the way?
-
- From https://github.com/ruby/psych/issues/730 and https://github.com/nobu/rdoc/actions/runs/14969443434/job/42046842539#step:5:35
```
Error: test_accept_blank_line(RDocMarkupToAnsiTest): LoadError: 127: The specified procedure could ... -
10:28 AM Revision 7517d762 (git): [DOC] Fix a link and sort links in NEWS.md
-
- 10:02 AM Revision 425fa0ae (git): Make `waiting_fd` behaviour per-IO. (#13127)
- - `rb_thread_fd_close` is deprecated and now a no-op.
- IO operations (including close) no longer take a vm-wide lock. -
-
07:57 AM Feature #21308: Replacing the Float#to_s (dtoa.c) implementation with a modern algorithm
- The change in https://github.com/ruby/json/pull/768 was an easy win, because the previous implementation was calling into question`Float#to_s` via `rb_funcall`. The overhead of doing so is so extreme, that any implementation that would s...
-
- @akr the test is insufficient, you should probably update RubySpec too.
-
-
-
- 05:13 AM Revision c4055709 (git): Update default gems list at cd7495a1d0e003360c96bb9746c1a8 [ci skip]
-
- Report EOF when applicable instead of an empty fragment.
Also stop fragment extraction on first whitespace.
https://github.com/ruby/json/commit/cc1daba860 -
- https://github.com/ruby/json/commit/f3dde3cb2f
-
- https://github.com/ruby/json/commit/41f1f6939d
-
- https://github.com/ruby/json/commit/30e35b9ba5
-
- https://github.com/ruby/json/commit/832b5b1a4c
-
- 18d395e0784401585b5c14300e689de55e208647
-
03:22 AM Bug #21280 (Closed): StringIO#set_encoding warns when backed by chilled string literal
- Fixed by commit:18d395e0784401585b5c14300e689de55e208647
-
03:20 AM Revision 5e59ae18 (git): [ruby/stringio] Fix Ruby 3.4 check
- https://github.com/ruby/stringio/commit/a27c5d5e2e
Co-authored-by: Sutou Kouhei <[email protected]> -
- StringIO does not warn for unchilled unfrozen string or for frozen
string, so it should not warn for chilled string.
https://github.com/ruby/stringio/commit/4ac33b8c70 -
- Fix C23 (GCC 15) WIN32 compatibility for rb_define_* functions
Fixes [Bug #21286] -
- ruby_3_2 commit:53c09781495b0096eec88e4268a48a13b245097a merged revision(s) commit:719486a642f0e282b02b958069b8b39b85b3aa1e.
-
02:05 AM Revision 9b8c846b (git): Add an additional test to module_eqq
-
- Fixed by commit:203199251f723d02f23f5782523d16f91277ea82
-
- This overrides Enumerable#to_h, but doesn't handle a block, breaking
backwards compatibility.
Set#to_h was added in the marshalling support commit, but isn't
necessary for that, as the underlying function is called. Remove
the method de... -
05/12/2025
-
- Sorry, I didn't get a chance to review this before it was merged. I really don't think adding this level of indirection to RCLASS_EXT access and similar is a good idea.
Let's look at `rb_class_get_superclass` as an example. This shoul... -
-
09:59 PM Feature #21311: Namespace on read (revised)
- As another datapoint on Linux (Ubuntu 24.04, AMD Ryzen 9800X3D), it looks like it is slower (around 0-5%) but also has higher memory usage by about 5-10%.
```
pre-namespace: ruby 3.5.0dev (2025-05-11T03:09:26Z master 49742414f6) +PRI... -
- byroot (Jean Boussier) wrote in #note-75:
> > Please open another ticker for further problems, issues, bugs, etc.
> ...
I had a plan to add CI configuration to add `RUBY_NAMESPACE=1` checks and I thought it would not be a part of this.... -
- > Please open another ticker for further problems, issues, bugs, etc.
Right now `RUBY_NAMESPACE=1 make -j btest` fails, are you actively working on adding a CI step that run with `RUBY_NAMESPACE=1` or should I open another ticket to t... -
- I've merged the change into master. So, let me close this issue.
Please open another ticker for further problems, issues, bugs, etc. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- I will :) I'm planning to cut an early Ruby 3.4 release this week.
-
10:02 AM Bug #21286: Windows - MSYS2 just updated to GCC 15.1.0, builds failing
- Will you create new ruby stable releases in the next days? I'm asking because I've seen many CI failures and bug reports due to this GCC-15 issue and I wonder if I should release a new RubyInstaller series with this patch or if there wil...
-
- 04:22 PM Revision 03a7f1ff (git): Update default gems list at 957473d87fc7741c8d36caed8f05db [ci skip]
-
- https://github.com/ruby/psych/commit/b9dec9f811
-
04:19 PM Revision 0c94ae04 (git): [ruby/psych] Fix dumping `StringIO` (and potentially others) on Ruby <= 2.7
- In Ruby < 3.0, the superclass of StringIO was actually already `Data`,
but it doesn't have the expected shape. So, on these earlier versions it errors:
> NoMethodError: undefined method `members' for #<StringIO:0x00005641dd5f2880>
> ...
... -
-
-
03:13 PM Feature #21258: Retire CGI library from Ruby 3.5
- CGI may be an "old" protocol but that maturity brings stability. It means I don't need to run an app server process (like puma) at all. I don't need to worry about open ports, memory leaks, resource leaks, connection pooling, etc. It's e...
-
-
- It's already defined in internal/sanitizers.h.
-
-
- https://github.com/ruby/erb/commit/9152ce8db4
-
-
-
-
-
- Fix Visual C warnings:
```
iseq.c(3793): warning C4312: 'type cast': conversion from 'int' to 'void *' of greater size
iseq.c(3794): warning C4312: 'type cast': conversion from 'int' to 'void *' of greater size
``` -
- Fix Visual C warnings:
```
regenc.h(121): warning C4067: unexpected tokens following preprocessor directive - expected a newline
``` -
- When the test is repeated 20 or more times in the same process
it's not that unlikely for `rand(100_000)` to return the same thing
twice, causing `TestObjectIdTooComplexClass` to fail.
```
1) Failure:
TestObjectIdTooComplexClass#test_... -
- 02:09 AM Revision 4464cbe5 (git): [rubygems/rubygems] Fix doctor command parsing of otool output
- I have several gem dylibs that have a line matching "(compatibility "
with no file path preceding it.
https://github.com/rubygems/rubygems/commit/de9dc2bdc4 -
- e.g.
```
JSON.dump(1746861937.7842371)
```
master:
```
"1.https://github.com/ruby/json/commit/746861937784+9"
```
This branch and older json versions:
```
https://github.com/ruby/json/commit/1746861937.7842371
```
In the end it's shor...
05/11/2025
-
- Or, use GCC 14 for a while, if possible. (I am not familiar with MSYS2)
-
- I believe this is the same issue as #21286.
Please apply the patch of https://github.com/ruby/ruby/pull/13202 yourself, or wait for Ruby 3.3.9. -
03:27 PM Bug #21328 (Closed): Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
- We are facing an issue that starts in 05/03/2025
We have an Azure Devops Pipeline that build and test a project, but in the test step we have the following error:
```
Gem::Ext::BuildError: ERROR: Failed to build gem native extension... -
- ../namespace.c: In function ‘current_namespace’:
../namespace.c:221:48: warning: ‘proc_ns’ may be used uninitialized [-Wmaybe-uninitialized]
221 | if (permit_calling_builtin || (proc_ns && NAMESPACE_USER_P(proc_ns))... -
- GC can trigger while we build the table, and if it sweeps an object
with an ID, it may not find it in the `id_to_obj` table. -
-
-
- This reverts commit 2a9236366d6016738a756caecab03263565a20c7.
spec/ruby/optional/capi/spec_helper.rb doesn't work well for mingw. -
- winpthreads-git 12.0.0.r720 provides `clock_gettime` and
`clock_getres` as inline functions. -
- The intial complex shape implementation never allowed objects
other than T_OBJECT to become too complex, unless we run out of
shapes.
I don't see any reason to prevent that.
Ref: https://github.com/ruby/ruby/pull/6931 -
05:02 PM Feature #21219: `Object#inspect` accept a list of instance variables to display
- ℹ️ In case it's of interest/inspiration, I released [Inspectable](https://alchemists.io/projects/inspectable) 0.2.0 which tackles what is described in this issue by making it easy to redact sensitive information, slim down verbosity, or ...
-
04:32 PM Misc #21325: make ruby more middle-aged man friendly
nobu (Nobuyoshi Nakada) wrote in #note-2:
> `format` is an alias of `#sprinf` inherited from `Kernel`.
> ...
if format is not ok,
to_s will be good, like Integer, `255.to_s(16)`-
- `format` is an alias of `#sprinf` inherited from `Kernel`.
We can't rename it. -
- > wanted to make sure everyone is aware of this
What I want all in the thread to realize is that if somewhere in the tree of your object, some code relies on a core extension, that object is automatically not cross-namespace-safe, and y... -
- Example:
```ruby
# main.rb
class C
attr_reader :target
def initialize(target)
@target = target
end
end
ns = Namespace.new
ns.require_relative 'foo'
c = C.new(Object)
ns::Foo.new.m(c)
# foo.rb
class Foo
def m(c)
(c.... -
- fxn (Xavier Noria) wrote in #note-70:
> Maybe you have the C code in your head, I am looking at it as a Ruby programmer would. I have one object reference, and I pass it in method call, no namespace-level constant resolution involved in... -
- > That should not happen, and if it happens, it's a bug. Could you write and show the script to reproduce it?
Exactly, as far as I can tell it does not happen, which to me it means we do not have (1) in place.
It was a way to say that,... -
- fxn (Xavier Noria) wrote in #note-68:
> @tagomoris when I said that (1) would break Ruby semantics I meant that **in the same namespace** you would have two objects with the same ID and different state. That does not happen as far as I ... -
- @tagomoris when I said that (1) would break Ruby semantics I meant that **in the same namespace** you would have two objects with the same ID and different state. That does not happen as far as I can tell.
-
- @tagomoris From the point of view of the Ruby programmer, I have an object, I pass it, and the callee receives a different object. To me, that is (2). Somehow, the object itself has mutated.
We are not talking about constant lookup in t... -
- @fxn I'm unsure I correctly understand what you mean... Let me check your point.
You said:
* The current namespace implementation behaves like (2), not (1).
* The passed value to `ns::C.x` (in the callee namespace side) will be a di... -
- Some of the issues I have noted seem to be addressable and have been added to the TODO. (I have written tickets for them.)
But there is [one](https://bugs.ruby-lang.org/issues/21322) that seems fundamental and worries me. Since this tic... -
- @byroot Thank you for working on the feature. I'll merge the patches soon (had merged one already).
About the crash with `RUBY_NAMESPACE=1`, I'll work on it ASAP after merging the branch once.
I know that the 3-5% performance degrada... -
- Alright, so I can't benchmark with `RUBY_NAMESPACE=1` because I keep running into that crash and can't figure it out.
In the process of trying to find a fix I found multiple other bugs:
- https://github.com/tagomoris/ruby/pull/7
... -
- I submitted a fix for the crash here: https://github.com/tagomoris/ruby/pull/5
But now it's crashing in `require`
```
/Users/byroot/.gem/rubies/head-namespaces/gems/activesupport-7.2.2.1/lib/active_support/inflector/inflections.rb... -
- headline benchmarks (in non-ideal conditions, I was on battery, etc) and **whithout** `RUBY_NAMESPACE=1`:
```
master: ruby 3.5.0dev (2025-05-11T03:09:26Z master 49742414f6) +PRISM [arm64-darwin24]
namespace: ruby 3.5.0dev (2025-05... -
- Trying to run benchmarks with `RUBY_NAMESPACE=1` crashes during init:
```
opt/rubies/head-namespaces/bin/ruby: [BUG] Segmentation fault at 0x0000000000000008
ruby 3.5.0dev (2025-05-11T00:30:16Z namespace-on-read-.. 6629795fff) +PRIS... -
- I opened a PR on yjit-bench with workarounds for both the fiddle issue and the CGI issue: https://github.com/Shopify/yjit-bench/pull/363
I'll see if I can benchmark your branch. -
- > bin/rails aborted!
> ...
Yes, the `cgi` changes broke Rails. You can add `gem "cgi"` to the benchmark's Gemfile to workaround that.
Both Rails nightly CI and Shopify nightly CI are still broken from the recent Set change and got br... -
- `make yjit-bench` is now failing even on master HEAD.
> bin/rails aborted!
> ...
I saw commits to re-organize cgi.
Hmm, I can wait for the fix and will make benchmark outputs if others don't make changes which conflict with the name... -
- We have followed the discussion in https://bugs.ruby-lang.org/issues/21311.
I may contribute a doc patch to explain the scope to which root object references behave differently in different namespaces.
A consequence of this design is t... -
- The third option is more aligned with my intuitive idea of a new entity with new rules. Instead of a container of methods and constants that `::` can work with, you may need a new kind of language-level entity an "isolate", a "cell", a "...
-
- @eregon maybe, but the fact is that you pass an object, and the callee receives a different object. This is not consistent with the current language.
Ideas:
* Introduce the concept of "namespace-level root objects", documented to be sw... -
-
- https://github.com/tagomoris/ruby/pull/7
RUBY_TYPED_FREE_IMMEDIATELY can be added because namespace_entry_free does no IO nor
things to block. -
- If we're referencing the namespace object we have to mark it.
-
-
- ```
/opt/rubies/head-namespaces/bin/ruby(sigsegv+0x84) [0x104e897e8]
/usr/lib/system/libsystem_platform.dylib(_sigtramp+0x38) [0x18de56de4]
/opt/rubies/head-namespaces/bin/ruby(object_id+0x80) [0x104d7d420]
/opt/rubies/head-namespaces/bi... -
-
-
-
-
-
-
-
-
- The macro RCLASS_EXT() accesses the prime classext directly, but it can be
valid only in a limited situation when namespace is enabled.
So, to prevent using RCLASS_EXT() in the wrong way, rename the macro and
let the developer check it i... -
- To make RClass size smaller, move flags of prime classext readable/writable to:
readable - use ns_classext_tbl is NULL or not (if NULL, it's readable)
writable - use FL_USER2 of RBasic flags -
-
-
-
- `rb_define_private_method` performs strict type checking on the function
pointer. As a result, we cannot pass the function a generic signature.
```
/github/workspace/src/namespace.c:1097:72: note: expected 'VALUE (*)(void)' {aka 'long... -
- ```
/github/workspace/src/proc.c:2023:65: error: format specifies type 'void *' but the argument has type 'const rb_namespace_t *' (aka 'const struct rb_namespace_struct *') [-Werror,-Wformat-pedantic]
2023 | rb_bug("Unexpected ... -
-
-
- ```
internal/class.h:158:20: warning: ‘RCLASS_SET_CLASSEXT_TABLE’ declared ‘static’ but never defined [-Wunused-function]
158 | static inline void RCLASS_SET_CLASSEXT_TABLE(VALUE obj, st_table *tbl);
| ^~~~~~~~... -
- ```
namespace.c: In function ‘rb_namespace_available’:
namespace.c:55:1: warning: old-style function definition [-Wold-style-definition]
55 | rb_namespace_available()
| ^~~~~~~~~~~~~~~~~~~~~~
``` -
-
- This reverts commit 585598623da949c92d0f2ea94029a863142ec908.
This broke Windows CIs
```
linking miniruby.exe
Creating library miniruby.lib and object miniruby.exp
process.obj : error LNK2019: unresolved external symbol clock_gettim...
05/10/2025
- 10:07 PM Revision 915d0277 (git): Fix typo (newsString -> new String)
-
10:01 PM Bug #21327 (Closed): Windows builds seem broken after clock_gettime changes?
- https://github.com/ruby/ruby/actions/workflows/windows.yml
not sure how stable windows normally is, but this looks consistent since this commit (5855986)
Assigning to nobu to investigate. -
- Diff instructions using:
```sh
DUMP="puts RubyVM::InstructionSequence.compile(ARGV.first).disasm.gsub(/^\d+ /, '')"
RUBY="def a(x, ...); b(...); end"
env -u RUBYOPT \
diff -U99 \
<(./build/ruby -v --parser=parse.y -e "$... -
- after 35, I lose all interests about programming.
no linux, no vim, no iterm2, and no much much.
when I want to format a ruby time to string.
I will try `Time.now.format("yy-MM-dd")`,
but I get `private method 'format' calle... -
05:32 PM Revision 98667f82 (git): [DOC] Update documentation for ObjectSpace#each_object
- Co-authored-by: Benoit Daloze <[email protected]>
- 05:32 PM Revision 29b3d683 (git): [DOC] Make clear that current behavior is not ideal
- 05:32 PM Revision a51b4a86 (git): [DOC] ObjectSpace#each_object behavior in multi-Ractor mode
- This behavior of ObjectSpace#each_object has been around since Ruby 3.0
when Ractors were first introduced, but was never documented and has
caused some amount of confusion:
https://bugs.ruby-lang.org/issues/17360
https://bugs.ruby-lang... -
- kou (Kouhei Sutou) wrote in #note-54:
> > building fiddle fails
> ...
I couldn't find the log when fiddle is built during `make yjit-bench`...
Anyway, I'll retry yjit-bench on Linux. -
- @mame
> I am personally excited to see Ruby adding a bold new feature that brings real energy and discussion to the community. This is Ruby. Let's enjoy this moment and move forward together with excitement.
Absolutely.
I would have w... -
09:03 AM Feature #21311: Namespace on read (revised)
- > building fiddle fails
Could you share the error message? -
- > So I ran benchmark/app_fib.rb
Fibonnaci isn't a very interesting benchmark here. It's just the same method being called over and over.
`yjit-bench` contains some macro benchmark that are more likely to have inline cache misses he... -
- On my laptop, building fiddle fails and it prevents running `make yjit-bench`.
So I ran benchmark/app_fib.rb and got results (The result after several times continuous runs):
```
# Ruby 3.4.2
$ time ruby benchmark/app_fib.rb
... -
- This allow to get or set fields without having to worry about the
shape type. -
- To be consistent with `rb_obj_field_set`.
-
- > It means CGI is not promoted bundled gems.
Is there a reason to skip this step?
For previous extractions we could rely on warnings to keep track of gems that need to be updated while continue to test ruby-head, with this immedi... -
- RubyGems has tons of mutable state, isn't core library and isn't "builtin classes" either, so it should not be in root Namespace, but it is currently:
```
$ RUBY_NAMESPACE=1 ruby -ve 'ns = Namespace.new; p ns::Gem.equal?(Gem)'
ruby 3.... -
- Looks somewhat similar, `benchmark` loads fine in main namespace but not in other namespace:
```
$ RUBY_NAMESPACE=1 ruby -ve 'require "benchmark"; p Benchmark::VERSION; ns = Namespace.new; File.write "ns.rb", "require :benchmark.to_s; ... -
- ```
$ irb
irb(main):001> 6 * 7
=> 42
$ RUBY_NAMESPACE=1 irb
/home/eregon/prefix/ruby-master/bin/ruby: warning: Namespace is experimental, and the behavior may change in the future!
See doc/namespace.md for know issues, etc.
/hom... -
- Seems very related to https://bugs.ruby-lang.org/issues/21322 so let's keep this one closed and discuss there.
-
- Full reproducer, showing that even though `Object` is the same reference in all namespaces it can have different constants in different namespaces, but only if calling `constants` in that namespace:
```
$ RUBY_NAMESPACE=1 ruby -ve 'ns ... -
-
- @byroot, if you will, I believe this one can be closed too.
-
- I suspect this one was an error of mine. I think we can close.
-
- Did you actually test the code? `mod1.constants == mod2.constants` returns `true`.
```
$ cat main.rb
ns = Namespace.new
mod1 = Object
mod2 = ns::Object
p mod1 #=> Object
p mod2 #=> Object
p mod1.object_id == mod2.object_id #=... -
- Right, IOW it's the duality between builtin classes and other classes.
Builtin classes' constants, methods, ivar and cvars are all a copy per Namespace (and so potentially differ), even though for all builtin classes they are `equal?` w... -
- For example, if I instead do
```ruby
ns = Namespace.new
ns.require_relative 'foo'
c = Class.new
c::X = 1
ns::C.x(c)
```
then `obj::X` resolves as expected in the method.
Method calls somehow seem to be swapping `VALUE`s that correspo... -
- > I believe this is consistent with the feature
I say so in the sense that objects with the same ID are equal in the namespace.
However, it could be argued that it is not consistent with Ruby.
`Object` is a constant that stores a clas... -
- @tagomoris thanks for the docs under `doc/namespace.md`.
Unless I missed it, I believe there is an edge case related to builtin classes (using the vocabulary there). Consider:
```ruby
# test.rb
ns = Namespace.new
ns.require_rela... -
- Full repro:
```
# Copy the description program to program.rb, e.g. $ xsel -b > program.rb
$ RUBY_NAMESPACE=1 ruby -ve 'puts "in main"; require "./program"; puts "in namespace"; Namespace.new.require "./program"'
ruby 3.5.0dev (2025-... -
- This is probably a consequence of https://bugs.ruby-lang.org/issues/21318.
-
- Right I think in the namespace defining the class/module the `Module#name` needs to not have a prefix, or it will break many gems.
OTOH when used outside, it could be very confusing without a prefix.
> suggested that Class#name shoul... -
- Main problem here is that there are many programs that depend on that name.
They may store it somewhere for later `const_get`. For example, [polymorphic Active Record associations](https://guides.rubyonrails.org/association_basics.html#... -
- This is definitely not ideal. `Class#name` could end up referring to a different constant.
```ruby
# main.rb
NS = Namespace.new
NS.require "./sub"
# sub.rb
class C; end
p C #=> expected: C
#=> actual: NS::C ← This could r... -
- Complete reproducer:
```
$ RUBY_NAMESPACE=1 ruby -ve 'p Module.nesting; ns = Namespace.new; File.write "ns.rb", "p Module.nesting"; ns.require "./ns"'
ruby 3.5.0dev (2025-05-10T07:50:29Z namespace-on-read-.. bd4f57f96b) +PRISM [x86_64... -
- > and sorry for the noise.
It's alright, even if the feature is experimental, the sooner bugs are noticed the better. So thank you for experimenting. -
- Yes, please, and sorry for the noise.
-
- > cannot repro anymore.
Closing then? -
- I was yesterday running a checkout from May 6. Updated the branch now and cannot repro anymore.
-
- @mame I was here till 4 AM experimenting with this feature.
To be organized, I reported different things in different tickets. These two could be related, but I don't know it. If they are, they will be closed together. -
- I don't think it's really necessary to create a separate ticket for this from #21319, is it?
-
-
- I was yesterday running a checkout from May 6. Updated the branch now and cannot repro anymore.
-
- I cannot repro the issue.
```ruby
# main.rb
ns = Namespace.new
ns.require "./sub"
p :success
```
```ruby
# sub.rb
module M
end
class C
include M
end
```
```
$ RUBY_NAMESPACE=1 ./miniruby main.rb
./miniruby: w... -
- winpthreads-git 12.0.0.r720 provides `clock_gettime` and
`clock_getres` as inline functions. -
- 06:59 AM Revision 3c37d6ff (git): Update bundled gems list as of 2025-05-09
-
05/09/2025
-
- Maybe the root cause is _enabling_ namespaces with `RUBY_NAMESPACE=1`.
-
- The following program
```ruby
module M
end
class C
include M
end
```
fails under a namespace with error
```
'Module#include': Cannot include refinement (TypeError)
``` -
- Maybe the root cause is _enabling_ namespaces with `RUBY_NAMESPACE=1`.
-
- The program
```ruby
module M
end
class C
extend M
end
```
fails under a namespace with error:
```
'Kernel#extend': Cannot extend object with refinement (TypeError)
``` -
- This avoids a race condition where we were clearing the cache from
another ractor while it was in use. Oops!
Fixes this failure http://ci.rvm.jp/results/master@oci-aarch64/5750416 -
- The following program
```ruby
X = :top
class C
X = :super
end
class D < C
p X
end
```
prints `:super` normally, and `:top` if running under a namespace. -
- Namespaces are not transparent for this program:
```ruby
Module.nesting
```
The nesting is empty or not depending on whether it is being executed under a namespace. - 10:13 PM Revision 87b621bd (git): Update default gems list at 58c008e68f31a8056df508cc46e17c [ci skip]
-
- https://github.com/ruby/psych/commit/dbf9e36583
-
- Namespaces are not transparent for this program
```ruby
if mod1.object_id == mod2.object_id
mod1.constants == mod2.constants
end
```
because it may fail for `mod1 = Object; mod2 = ns::Object`, which have the same object ID. -
- Namespaces are not transparent for this program
```ruby
C = Class.new
C.name == 'C'
```
because under a non-main user namespace, the name of `C` has the namespace as a prefix. -
10:01 PM Feature #15408: Deprecate ObjectSpace._id2ref
- > The question is rather why you want _id2ref to be deprecated
I want it removed, actually! 😀
You have seen all the reasons why it is problematic, but on top of all that it was never intended to be an official API in the first plac... -
08:20 PM Feature #15408: Deprecate ObjectSpace._id2ref
- headius (Charles Nutter) wrote in #note-44:
> I'd also like to know **why** you want `_id2ref` to stick around.
I think that question is backwards. There is no need for any reason to keep existing functionality; backward compatibilit... -
- Applied in changeset commit:git|4de049a3f9709ab8b0b192c40e83b910b80d6de3.
----------
Deprecate `ObjectSpace._id2ref`
[Feature #15408]
Matz decided to deprecate it for Ruby 2.6 or 2.7 but that never
actually happened.
Given the object... -
- I was hoping for a removal timeline, but alright. I'll merge my PR.
-
- This was discussed at the dev meeting, and @matz agreed to add the deprecation warning.
-
- * The begp, lenp and stepp might not be written to, so they need default values.
-
- * Since it does not work when using some configure options such as:
.../configure --with-ext=-test-/cxxanyargs,+ --enable-shared
as the CI does.
* It also duplicates the logic of spec/ruby/optional/capi/spec_helper.rb incorrectly.
... -
09:22 PM Revision 29be534f (git): Try fixing building C API specs with make
- * But it doesn't work because there is no .ext/include/ruby/digest.h
when using .../configure --with-ext=-test-/cxxanyargs,+ --enable-shared
as the CI does. -
-
-
-
- Eregon (Benoit Daloze) wrote in #note-3:
> it clearly seems to exhibit that behavior
To clarify what I mean:
```
$ ruby -e 'OBJ = Object.new; ObjectSpace.define_finalizer(OBJ) { puts "finalizer ran" }'
finalizer ran
```
But clea... -
- > When a Ractor terminates just before it actually does so it should probably run the remaining finalizers
Objects aren't necessarily unreferenced/garbage collectable at this point (they could have been made shareable, or be the retur... -
- When a Ractor terminates just before it actually does so it should probably run the remaining finalizers, AFAIK, this is what CRuby does when the process is about to terminate and there are finalizers not run yet (but I might be wrong, t...
-
- > Run each finalizer in the Ractor that created it (what do we do about terminated ractors?)
That one I think would be doable, we could record the current ractor in with the finalizer.
For terminated Ractors I don't think it's a bi... -
- It does seem like it's a problem that this is a way to have access to an unshareable object from multiple ractors
``` ruby
def build_finalizer(object)
previous_ractor = Ractor.current
proc { puts "finalizing on #{Ractor.current} (wa... -
- Reproduction (with assertions enabled):
```ruby
require "tempfile"
Ractor.new do
10.times do
Tempfile.new
end
end.take
GC.start
```
```
<OBJ_INFO:rb_ractor_confirm_belonging@../src/ractor_core.h:375> (File)
... -
-
- This feature proposal is quite exceptional. Because this is a feature strongly driven by @matz himself, and Ruby is matz's language.
@tagomoris has been working closely with Matz for several years to design and implement it. Although ... -
- Let me add.
This is not a case of "let's merge and polish". Problem is, it has to be seen if you can satisfy the goals with this approach at all. Because, you cannot be dazzled by the stated goals, you have to carefully check if the goa... -
- I am aligned with @eregon.
There are several important issues.
Another one that has not been mentioned (I think) is that the design trivially allows for two objects with the same object ID to be different entities. The Ruby programmer ... -
- In https://github.com/ruby/dev-meeting-log/blob/master/2025/DevMeeting-2025-05-08.md#discussion
> mame: Are there any strong opponents?
I guess I am one.
There are many concerns from several people that have been raised here, many unans... - 05:53 PM Revision e2f5e233 (git): [ruby/psych] exception tests
- https://github.com/ruby/psych/commit/1e9b79f699
- 05:53 PM Revision 42328d4e (git): [ruby/psych] more special cases
- https://github.com/ruby/psych/commit/b33bf8b060
- 05:53 PM Revision 451e1dcf (git): [ruby/psych] duplicate more tests
- https://github.com/ruby/psych/commit/a3be6429bf
- 05:53 PM Revision ae299cc9 (git): [ruby/psych] add first test for safe load stream
- https://github.com/ruby/psych/commit/336553b412
- 05:53 PM Revision f0e2a41d (git): [ruby/psych] fixed bugs from testing
- https://github.com/ruby/psych/commit/e954f96639
- 05:53 PM Revision d6931930 (git): [ruby/psych] Add safe version for load_stream
- https://github.com/ruby/psych/commit/30a2a5ee94
-
- There's a lot of warnings when running test_objectspace.rb because of
ObjectSpace._id2ref. For example:
test_objectspace.rb:19: warning: ObjectSpace._id2ref is deprecated -
-
- Applied in changeset commit:git|f30f0f0a22bb5cf536b5ca551f3dfa5ebb745030.
----------
Fix crash when instantiating classes in Ractors
[Bug #18119]
When we create classes, it pushes the class to the subclass list of the
superclass. This... -
- [Bug #18119]
When we create classes, it pushes the class to the subclass list of the
superclass. This access needs to be synchronized because multiple Ractors
may be creating classes with the same superclass, which would cause race
cond... -
-
- With recent commits, it seems that a cgi.gemspec is not created.
erb.gemspec shows it as a dependency? -
- We discussed this in devmeeting.
We decided the followings:
* To remove `cgi` library without `CGI.escape*` and `CGI.unescape*` methods.
* It includes `escapeURIComponent`, `unescapeURIComponent`, `escapeHTML`, `unescapeHTML`, `... -
- https://github.com/ruby/stringio/pull/132 is a much cleaner solution, was it considered?
(https://bugs.ruby-lang.org/issues/21281 doesn't have the log yet so I can't check that, EDIT found it: https://github.com/ruby/dev-meeting-log/blob... -
- Discussed at the dev meeting. @matz said that he prefers not to issue warnings that could be false positives, even if they are true positives in many cases.
The code `StringIO.new("").set_encoding('binary')` will work even in future a... -
- Followup: https://github.com/ruby/ruby/pull/13286
-
- As well as `RB_OBJ_SHAPE_ID` -> `rb_obj_shape_id`
and `RSHAPE` is now a simple alias for `rb_shape_lookup`.
I tried to turn all these into `static inline` but I'm having
trouble with `RUBY_EXTERN rb_shape_tree_t *rb_shape_tree_ptr;`
not... -
-
-
-
- And `rb_shape_get_shape` -> `RB_OBJ_SHAPE`.
-
-
- Also rename it, and change parameters to be consistent with
other transition functions. -
- It's more consistent with other transition functions.
-
-
-
-
-
-
-
-
-
- As well as `rb_shape_edges_count` and `rb_shape_memsize`.
-
-
-
- Duplicate of: [Bug #20271] [Bug #20267] [Bug #20255]
This was fixed in 0350290262ea0fbc4e1807901797ee8a6970c2b9 and a few followups.
-
- The linked PR was merged.
-
- After fork we reset to single ractor mode (which IMO we shouldn't do,
but it requires more work to fix) and so we need to add the pending
object counts back to the main heap. -
- [Feature #15408]
Matz decided to deprecate it for Ruby 2.6 or 2.7 but that never
actually happened.
Given the object_id table is a contention point for Ractors
it seems sensible to finally deprecate this API so we can
generate and stor... -
- Meeting log is here: https://github.com/ruby/dev-meeting-log/blob/master/2025/DevMeeting-2025-04-15.md
-
- > Should I create a ticket here?
You can directly open a PR on https://github.com/ruby/net-http/.
If it doesn't get noticed after a while, you can open a corresponding ticket here. -
- > Maybe Net::HTTP could use `IO.select`?
That sounds like a good idea and I'd like to try it. I have checked some previous attempts. Should I create a ticket here? -
- 05:28 AM Revision dcd0a35c (git): Update default gems list at d3c472781dec4fe415203fbb898d8b [ci skip]
-
-
-
-
-
-
-
-
-
-
-
-
- I also ran into this, so I opened an pull request document this behavior.
https://github.com/ruby/ruby/pull/13278 -
- While discussing #21154 with some people at the dev meeting, I found a weird behavior of `Kernel#autoload` that's hard to explain.
I haven't yet looked at it carefully, but I was asked to create a ticket anyway.
```ruby
# main.rb
a... -
-
- This was discussed at the dev meeting, but @matz was negative about adding this warning. He prefers fluent code over performance, so from Ruby's perspective, he did not want to encourage rewriting:
```ruby
order!(argv, **keywords, &n... -
-
- Discussed at the dev meeting. This proposal was accepted as `struct: true` keyword argument, like
```ruby
Time.new(2025, 2, 29, 0, 0, 0, "+00:00", strict: true) #=> ArgumentError
``` -
- Discussed at the dev meeting, and @matz said "go ahead".
05/08/2025
-
- Fixed by a5ba7124bcc112f537a29564f644dea67f2b532d
-
- Sorry @jeremyevans0 I think Aaron and I missed that PR, but we did the same thing in https://github.com/ruby/ruby/pull/12982 which should fix this.
One thing we didn't do that's in your PR is forbid forking from within a Ractor, but t... -
-
- I have a fix here: https://github.com/ruby/ruby/pull/13284
-
- Introduced in: https://github.com/ruby/ruby/pull/13159
Now that there is no longer a unique TOO_COMPLEX shape with
no children, checking `shape->type == TOO_COMPLEX` is incorrect. -
- @Dan0042 I think @Eregon covered what I was going to say, but I'd also like to know **why** you want `_id2ref` to stick around. There's generally better ways (more reliable, easier for VMs to implement) to everything I have seen it used ...
-
- https://byroot.github.io/ruby/performance/2025/04/26/unlocking-ractors-object-id.html explains the problems of `_id2ref` in details, and how it changed.
-
- @Dan0042 It still is, CRuby has to keep a weak map of all objects for which the object_id was asked in case `_id2ref` is used.
That's a big footprint and performance overhead.
It's also impossible to implement this efficiently, as the ... -
- The original reason to deprecate `_id2ref` is no longer relevant now that `object_id` is a monotonically-increasing ID. So I don't think it should be deprecated, unless there's some other benefit/reason that wasn't mentioned above.
-
- Ractor objects that are available in a child process should raise a
`Ractor::ClosedError` exception when called with `send` or `take`
Co-authored-by: John Hawthorn <[email protected]> -
- Ractors created in a parent process should be properly shut down in the
child process. They need their cache cleared and status set to
"terminated"
Co-authored-by: John Hawthorn <[email protected]> -
- Otherwise it might be held by another Ractor, causing a deadlock in the
new process. -
- ../variable.c: In function ‘iterate_over_shapes_with_callback’:
../variable.c:2189:1: warning: control reaches end of non-void function [-Wreturn-type]
2189 | }
| ^ -
05:31 PM Feature #20405: Inline comments
- There seems to be some revival of this in the context of type checkers, and Hiroya Fujinami graciously asked for my opinion on the Sorbet Slack. I'll chime into say this:
One of the best parts of Ruby is how much freedom it gives you at... -
- Using type checkers makes it difficult to write Ruby fluently. To make type checkers work effectively in Ruby, we need to add numerous annotations, and these annotations are done via comments. However, Ruby only has line comments. This r...
-
05:13 PM Bug #20957: RangeError on Array#values_at with negative ranges
- I found almost same behavior at Array#fill
```
[0,1,2,3].fill(10, -10..-5) #=> RangeError
[0,1,2,3].fill(10, -5..-3) #=> RangeError
[0,1,2,3].fill(10, -3..3) #=> [0, 10, 10, 10]
[0,1,2,3].fill(10, 3..10) #=> [0, 1, 2, 10, ... -
- Right.
I think it's quite valuable to make those `rb_undef_alloc_func` to avoid having to handle uninitialized objects because that means extra checks (performance overhead) and less optimizations.
For example if the Class#superclass i... -
- > Or core types could actually define dup & clone as overridden methods, and not use the alloc function at all and so use rb_undef_alloc_func().
That seems the cleanest actually, WDYT?
Yes. The only options that work are to `rb_undef... -
- I think it would be good to compare this to "isolated execution contexts" which is the well-known approach to get such isolation, e.g.:
* CPython has sub-interpreters
* V8 (JavaScript) has isolates
* MRuby has mrb_state/mrb_open() (ba... -
- I'll do that, thank you!
-
- fxn (Xavier Noria) wrote in #note-44:
> Congrats @tagomoris :).
> ...
Thank you :D
I'm totally open to consider changing the current behavior around permanent classpath including namespace.
But I'll focus on fixing some minor issue... -
- Congrats @tagomoris :).
Would you be open to consider having the permanent name of classes and modules be constant paths? -
- I added committer grants to @tagomoris. Please let me know if you have extra permission or something.
-
- > I nominate @tagomoris (Satoshi Tagomori) for committer.
+1 -
- @tagomoris Can you share your required/optional information to me? see https://github.com/ruby/ruby/wiki/Committer-How-To#required
-
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.
Matz. -
- osyoyu (Daisuke Aritomo) wrote in #note-5:
> I am not sure about this. Sending HTTP request using net/http inside an Ractor should be a valid use case, and `Timeout` is blocking this (it is internally used to implement `open_timeout` `r... -
- > if we got some shareable mutable state, then we'd need a shareable mutex
Come to think of it, I now do think that `Mutex`es themselves are not the problem. So yes I agree with you, and am okay to close this ticket (I can come back w... -
- This allows the default GC to not need debug_counter.h when building as a
modular GC. -
- We don't need to check for USE_DEBUG_COUNTER because the code is no-op
if USE_DEBUG_COUNTER is not enabled. -
-
01:30 PM Misc #21290: Unable to build ruby extension on Fedora 42 due to possible GCC 15 issues
- Just adding that I am also experiencing this with ed25519 and ruby-prof, as well as appsignal.
* **Ruby Version:** 3.3.5 (installed via `rbenv`)
* **Gem causing the issue:** `ed25519` (v1.3.9), `ruby-prof` (v1.7.1), `appsignal` (v4.5... -
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 reproduce the issue
https://github.com/mongodb/bson-ruby/discussions/351#discussioncomment-13059541 -
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 `ruby-prof`) on Ruby 3.4.3. The compilation fails with errors related to `bool` and `stdbool.h`, similar to what has been d... - 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: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.
This behavior breaks the code depending on the previous add_file
behavior.
Therefore, add_file accepts mtime as an argumen... -
- (https://github.com/ruby/strscan/pull/153)
Fix https://github.com/ruby/strscan/pull/152
CRuby can walk off the end because there's always a null byte. In JRuby,
the byte array is often (usually?) the exact size of the string. So we
nee... -
- (https://github.com/ruby/strscan/pull/150)
These parse methods take begin and end indices, not begin and length. A
test is included.
Fixes https://github.com/jruby/jruby/issues/8823
https://github.com/ruby/strscan/commit/9690e39e73 -
- https://github.com/ruby/json/commit/3b605d9b1e
-
- Use feature testing to detect native Set,
and don't rely on `Set#to_h` which wasn't intended
as a public method.
https://github.com/ruby/psych/commit/d58cff11af -
-
- ```
variable.c: In function ‘iterate_over_shapes_with_callback’:
variable.c:2188:1: warning: control reaches end of non-void function [-Wreturn-type]
2188 | }
| ^
variable.c: In function ‘rb_field_get’:
variable.c:... -
- Use `st_foreach_with_replace` rather than to call `st_insert`
from inside `st_foreach`, this saves from having to disable GC.
Co-Authored-By: Peter Zhu <[email protected]> -
-
- And get rid of the `obj_to_id_tbl`
It's no longer needed, the `object_id` is now stored inline
in the object alongside instance variables.
We still need the inverse table in case `_id2ref` is invoked, but
we lazily build it by walking ... -
- This opens the door to store more informations in shapes, such
as the `object_id` or object address in case it has been observed
and the object has to be moved. -
- Also refactor checks for `->type == SHAPE_OBJ_TOO_COMPLEX`.
-
- Ivars will longer be the only thing stored inline
via shapes, so keeping the `iv_index` and `ivptr` names
would be confusing.
Instance variables won't be the only thing stored inline
via shapes, so keeping the `ivptr` name would be conf... -
- > The term premature optimization typically refers to cases where you optimize, and later, the optimization results in a negative effect.
I have to disagree here. Premature optimization typically refers to cases where you optimize cod... -
- Dan0042 (Daniel DeLorme) wrote in #note-2:
> I appreciate the effort here, but I wonder if this might be a case of premature micro-optimization. Was there a measureable performance improvement from these changes? If the gains are neglig... -
- I appreciate the effort here, but I wonder if this might be a case of premature micro-optimization. Was there a measureable performance improvement from these changes? If the gains are negligible, we should be cautious about encouraging ...
-
- https://github.com/ruby/ruby/commit/ce51ef30df5bf07ec3881a377f0011b8f20ec507 broke
ext/-test-/econv/append.o. We should rebuild that object file when dependencies are updated. -
- byroot (Jean Boussier) wrote in #note-5:
> 99% of the time, when I use a bare `rescue` it's because I'll call `raise` again, or calling unknown code and I need to not crash, etc.
> ...
Fully agree with the above.
I understand the ra...
05/07/2025
-
- Eregon (Benoit Daloze) wrote in #note-12:
> Unless they truly need to communication at all between namespaces, but then different processes (or multiple interpreters in a process) might be a better trade-off (notably can run in parallel... -
- Basically, I believe the idea is to have isolated execution contexts without forking, but is hard to achieve that by subclassing Module and tweeking things. Could be wrong, but it is my hunch. As I said, I believe this might need a new e...
-
- tagomoris (Satoshi Tagomori) wrote in #note-28:
> Mounting server-less applications (run on AWS Lambda, separated on processes in production) on a single app server for development
Why not simply using different processes for that? C... -
- tagomoris (Satoshi Tagomori) wrote:
> Root namespace is a unique namespace to be defined when a Ruby process starts. It only contains built-in classes/modules/constants, which are available without any `require` calls, including RubyGem... -
- Aaron that is a concern I have also in mind that I have not expressed yer.
The current proposal allows access to the user namespaces from the creating one And believe some use cases in this thread re dogfood need that communication.
... -
- Eregon (Benoit Daloze) wrote in #note-12:
> * Any user-defined class instance won't be `is_a?` in another namespace and this might be particularly confusing for stdlib/default gems/bundled gems, e.g. a Date or Pathname created in `ns1` ... -
- Dan0042 (Daniel DeLorme) wrote in #note-19:
> I'm not sure if this can be achieved with TruffleRuby sub-interpreters or how you would go about it.
It's easy with sub-interpreters, you would create a sub-interpreter instead of a names... -
- @tagomoris thanks for your replies, even more with such a busy thread :). Let me followup:
> There should be no needs for library developers to consider such things.
Namespace is designed to isolate side effects of "the entry point of a... -
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 fringe needs.
Just was reminded of another gem I wrote that utilizes this pattern.
I use it two ways.
1. When I am wr... -
- Thank you for expanding on the motivation, the design makes more sense to me now.
I'm still not convinced the tradeoff is worth it, but at least it makes sense.
Out of curiosity, have to ran the `yjit-bench` suite? I know it's a pr... -
- @fxn
> So, I guess spawning does not create hierarchy. A namespace may not have a pointer to the namespace where it was born (or I don't see the need for it after creation). It is conceptually just one flat layer of independent user n... -
- I'm sorry that I skipped to make effort to describe the motivation and copied the motivation section from the past ticket (and it was not well described enough).
Let me explain the motivation in detail. I had some mixed points below:
... -
- I have compiled the branch and I am playing around a bit with `miniruby` to test my understanding of the feature.
Something that has caught my attention is that class and module names do not return constant paths. That is, the following... -
- FYI: you can try namespace PR on https://ruby.github.io/play-ruby/?run=14855772787&options=%7B%22arguments%22%3A%5B%5D%2C%22env%22%3A%7B%22RUBY_NAMESPACE%22%3A1%7D%7D&code=%0Adef+foo+%3D+%3Amain%0A%0Ans1+%3D+Namespace.new%0Ans1.require%2...
-
- mame (Yusuke Endoh) wrote in #note-10:
> @tenderlovemaking Can we close this?
Yes, sorry. I thought I had closed this.
Merged in 8ac8225c504dee57454131e7cde2c47126596fdc -
- Note: https://github.com/ruby/ruby/pull/13080 has been merged.
-
- @tenderlovemaking Can we close this?
-
- Backport [Bug #21286]
-
-
-
- * [Feature #21258] Retire CGI library from Ruby 3.5
* Can I remove CGI library without `CGI::Util` ?
* What's the preferred migration process?
1. We keep only cgi/escape (C impl)feature in Ruby.
2. We keep `cgi/util` with `c...