Activity
From 10/30/2021 to 11/05/2021
11/05/2021
-
07:06 PM Feature #18287: Support nil value for sort in Dir.glob
- Eregon (Benoit Daloze) wrote in #note-5:
> @jeremyevans0 Do you know any other core method with this behavior?
I ... -
06:38 PM Feature #18287: Support nil value for sort in Dir.glob
- @jeremyevans0 Do you know any other core method with this behavior?
I am sure they are many dozens that meet my crit... -
06:42 PM Misc #18266: DevelopersMeeting20211118Japan
- * [Feature #18287] Support nil value for sort in Dir.glob (eregon)
* Let's be consistent for core methods and trea... -
08:55 AM Misc #18266: DevelopersMeeting20211118Japan
- - [Feature #18273] `Class#subclasses`
- Something we forgot to discuss as part of [Feature #14394].
- There ar... -
03:22 PM Bug #18289 (Closed): Enumerable#to_a should delegate keyword arguments to #each
- Applied in changeset commit:git|e83c02a768af61cd0890a75e90bcae1119d8bd93.
----------
Delegate keywords from Enumerab... -
02:10 PM Bug #18289: Enumerable#to_a should delegate keyword arguments to #each
- I've submitted a pull request to fix this: https://github.com/ruby/ruby/pull/5086
-
11:11 AM Bug #18289 (Closed): Enumerable#to_a should delegate keyword arguments to #each
- `Enumerable#to_a` has always delegated its arguments to `#each`, but it does not handle keyword arguments. This seems...
-
03:21 PM Feature #18291: When use =~ with named group, if regex is on the right side, variable not defined.
- `regexp.rdoc` documents that the literal regexp must be on the left hand side in order to assign to local variables, ...
-
03:12 PM Feature #18291 (Open): When use =~ with named group, if regex is on the right side, variable not defined.
- Following code not work.
```rb
if "Billy Zheng" =~ /(?<first_name>\w+)\s+(?<last_name>\w+)/
p first_name
... -
02:01 PM Feature #18290 (Closed): Deprecate rb_gc_force_recycle
- # GitHub PR: https://github.com/ruby/ruby/pull/4363
I'm proposing to deprecate `rb_gc_force_recycle` and make it a... -
07:00 AM Bug #18288 (Third Party's Issue): Getting error while installing Pod
- I think this is the same issue as #17862, #17922, #17988, and #18071. See also https://github.com/typhoeus/ethon/issu...
-
06:34 AM Bug #18288 (Third Party's Issue): Getting error while installing Pod
- Getting below error while installing Pod.
You may have encountered a bug in the Ruby interpreter or extension libr...
11/04/2021
-
04:22 PM Bug #17106: Build ruby 2.6.6 from git source
- > I still see this build error on the latest ruby_2_6 branch (commit: 95ba9053e20ad8d113af37b3f1f4cbfff1f6a8f1).
`... -
03:33 PM Bug #17106: Build ruby 2.6.6 from git source
- I still see this build error on the latest ruby_2_6 branch (commit: `95ba9053e20ad8d113af37b3f1f4cbfff1f6a8f1`).
I n... -
02:36 PM Feature #18287: Support nil value for sort in Dir.glob
- Eregon (Benoit Daloze) wrote in #note-3:
> This is inconsistent with basically every Ruby method out there.
I dis... -
11:32 AM Feature #18287: Support nil value for sort in Dir.glob
- This is inconsistent with basically every +core+ Ruby method out there +taking a boolean/boolean-like argument+.
For... -
09:22 AM Feature #18287: Support nil value for sort in Dir.glob
- This is intentional and documented as:
```ruby
# The results which matched single wildcard or character set are s... -
09:17 AM Feature #18287: Support nil value for sort in Dir.glob
- `nil` means the default behavior, that is `sort: true`.
-
08:47 AM Feature #18287 (Closed): Support nil value for sort in Dir.glob
- Good day, everyone.
I would like to suggest (or question) the support of a `nil` value for `sort` argument in `Dir... -
02:00 PM Bug #18286: Universal arm64/x86_84 binary built on an x86_64 machine segfaults/is killed on arm64
- nobu (Nobuyoshi Nakada) wrote in #note-1:
> Could you try with the master, and show more backtraces?
Sure. Simila... -
07:14 AM Bug #18286: Universal arm64/x86_84 binary built on an x86_64 machine segfaults/is killed on arm64
- Could you try with the master, and show more backtraces?
-
01:19 PM Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)`
- Ah, maybe Koichi meant that `bind_call` doesn't change the default definee like `instance_exec` does?
i.e., does
``... -
01:13 PM Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)`
- byroot (Jean Boussier) wrote in #note-8:
> Assuming I correctly understand how it would work, then yes it would be g... -
11:39 AM Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)`
- > only as a replacement for instance_exec(&proc).
Assuming I correctly understand how it would work, then yes it w... -
01:16 PM Misc #18266: DevelopersMeeting20211118Japan
- * [Misc #18285] NoMethodError#message uses a lot of CPU/is really expensive to call (eregon)
* OK to do https://bu... -
09:34 AM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- Thanks Benoit for stating in very clear and exact terms what I was trying to express :)
11/03/2021
-
11:57 PM Bug #18243: Ractor.make_shareable does not freeze the receiver of a Proc but allows accessing ivars of it
- From #18276,
I think the best solution by far is `Ractor.make_shareable(proc.bind(nil))` (concise, clear, clean as it... -
11:54 PM Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)`
- Dan0042 (Daniel DeLorme) wrote in #note-6:
> Why not `proc.bind(obj).call` ? It seems a more "proper" API, more comp... -
11:46 PM Feature #12745: String#(g)sub(!) should pass a MatchData to the block, not a String
- The fix for #12689 seems clear, such variables need to be Thread-local (or even Fiber-local).
That's already what Tr... -
02:03 PM Feature #12745: String#(g)sub(!) should pass a MatchData to the block, not a String
- I would love to see this resurrected.
If you want the MatchData in a gsub block, at first it looks like you can j... -
11:39 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- Re special casing, true/false/nil are typically already special-cased for exception messages (because `#<TrueClass:0x...
-
04:33 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- My suggestion is indeed to only include the class + perhaps the pointer id or the object id for regular user classes,...
-
04:16 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- > I was trying to use that to make a case that perhaps the default should not be to use #inspect, not to use the insp...
-
12:06 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- > Well I for one complained about that limit, hence why I opened the ticket.
Right! Thanks for pointing it out.
... -
11:22 AM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- > I'm actually talking about NoMethodError, not NameError, so I don't think this issue is caused by the did you mean ...
-
09:15 AM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- #### Important note! I'm actually talking about **`NoMethodError`**, not **`NameError`**, so I don't think this issue...
-
09:52 PM Bug #18284: Macosx M1
- I'm not sure it's related, but a `pod` related error came up on the #ruby IRC channel today, and the user solved thei...
-
04:21 PM Bug #18286 (Closed): Universal arm64/x86_84 binary built on an x86_64 machine segfaults/is killed on arm64
- A universal arm64/x86_84 ruby binary for macOS built on a x86_64 machine segfaults/is killed when executed on an arm6...
11/02/2021
-
06:20 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- > we ran into this issue on one of our internal testing applications.
Let me confirm: you are facing this issue whe... -
03:53 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- If applicable, I suggest to do what we do in Rails: https://github.com/rails/rails/blob/f95c0b7e96eb36bc3efc0c5beffbb...
-
02:32 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- Yeah, I think it's useful to include the object class and possibly its id, but with the default `#inspect` behavior o...
-
12:50 PM Feature #18285: NoMethodError#message uses a lot of CPU/is really expensive to call
- I think we've had this report multiple times, it's a trade-off between efficiency and useful information being shown....
-
12:08 PM Feature #18285 (Closed): NoMethodError#message uses a lot of CPU/is really expensive to call
- Hello there! I'm working at Datadog on the ddtrace gem -- https://github.com/DataDog/dd-trace-rb and we ran into this...
-
12:46 PM Bug #18284: Macosx M1
- Although we have received several reports that `pod` did crash on M1 Mac (see e.g. #17922, #17988, #18043), I cannot ...
-
09:32 AM Bug #18284 (Rejected): Macosx M1
- crash at pod update
`{"app_name":"ruby","timestamp":"2021-11-02 10:17:47.00 +0100","app_version":"","slice_uuid":"72... -
10:59 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- @mame ah you beat me to it, I use a different approach but I don't know if it's any better than yours: https://github...
-
10:30 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- I've created a PR: https://github.com/ruby/ruby/pull/5070
-
08:46 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- Okay I cloud create a small repro case:
```
class C
end
100000.times { Class.new(C) }
p C.descendants
```... -
07:46 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- Thanks for working this issue. Glad to hear that it reproduces.
-
07:39 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- Argh, the message seems just a warning. I could run `bundle exec rake test` and reproduce the issue. Sorry for the no...
-
07:25 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- Thank you for the information, but neither works. How did you setup ruby and bundler? I just did:
```
git clone h... -
06:21 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- Thanks for taking care of it. In my environment `bundle install` just works fine.
then, how about using `bundle upda... -
05:26 AM Bug #18282: Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- Thanks for the detailed report. Maybe this is a newbie question of bundler, but `bundle install` failed as follows on...
-
03:26 AM Bug #18282 (Closed): Rails CI raises Segmentation fault with ruby 3.1.0dev supporting `Class#descendants`
- This report was originally reported at Rails https://github.com/rails/rails/issues/43574
then moved to bugs.ruby-lan... -
09:13 AM Bug #18283 (Rejected): Creating a subclass in Ractor dumps core
- ```
$ ruby -e 'class C;end; (1..10).map { Ractor.new { 100000.times { Class.new(C) } } }.each {|r| r.take }'
<inter... -
02:05 AM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- Hmm, looking at the source code there are those functions that thoughtlessly pass their arguments to `strlen()` witho...
-
12:59 AM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- Hello, I'm the one who wrote the comment in string.h.
- OK to remove `__attribute__((__nonnull__))` to revive `mus...
11/01/2021
-
11:08 PM Bug #18281: Ruby 3.1.0: gem uninstall -aIx fails to uninstall debug
- Oh also, interesting.. if I `gem install debug` and re-run `gem uninstall -aIx` it works!
```
gem uninstall -aIx
... -
11:05 PM Bug #18281 (Closed): Ruby 3.1.0: gem uninstall -aIx fails to uninstall debug
- 👋 So I'm not sure this is a bug with `debug` or rubygems, but thought I'd start here.
When running `gem uninstall... -
05:14 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- IMHO the gem should be fixed so it doesn't call `rb_utf8_str_new_cstr()` with NULL.
-
04:02 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- ukolovda (Dmitry Ukolov) wrote in #note-4:
> I'm afraid, we got many errors with other gems, which use clang and giv... -
03:04 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- That documentation was recently added: https://github.com/ruby/ruby/pull/4815 (hasn't been part of a release yet AFAICT)
-
01:39 PM Feature #18280 (Feedback): Allow rb_utf8_str_new_cstr(NULL)
-
01:10 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- It is documented that the parameter for `rb_utf8_str_new_cstr` (and also for its friends) [must not be a null pointer...
-
01:08 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- Thank you!
I've got this error when test gem `addressable` + `idn-ruby`.
See https://github.com/ukolovda/addressa... -
12:58 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- Compiling with `-fno-delete-null-pointer-checks` prevents this check from being optimised away. Using the test script...
-
12:41 PM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- `rb_str_new_cstr` seems to be attributed as `nonnull` since commit:091faca99ca92cb1146b3c4d8ebba67f4822561c. Thus it ...
-
10:44 AM Feature #18280: Allow rb_utf8_str_new_cstr(NULL)
- The SEGV reproduces for me with the following test case:
```ruby
require "fiddle"
include Fiddle
h = dlopen... -
07:06 AM Feature #18280 (Feedback): Allow rb_utf8_str_new_cstr(NULL)
- Ruby process crushed.
`
Addressable::URI when parsed from 'http://example.com/%E8'
/home/ukolovda/RubymineProjec... -
03:59 PM Bug #18243: Ractor.make_shareable does not freeze the receiver of a Proc but allows accessing ivars of it
- Dan0042 (Daniel DeLorme) wrote in #note-7:
> It's not uncommon for a proc to have behavior that is independent of `s... -
02:14 AM Bug #18243: Ractor.make_shareable does not freeze the receiver of a Proc but allows accessing ivars of it
- It's not uncommon for a proc to have behavior that is independent of `self`. Let's say:
Ractor.make_shareable... -
07:32 AM Feature #15667: Introduce malloc_trim(0) in full gc cycles
- Wouldn't that be a good feature in combination with GC auto_compaction? First run the auto_compaction against memory ...
-
02:44 AM Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)`
- Why not `proc.bind(obj).call` ? It seems a more "proper" API, more composable. You can bind once and then call multip...
10/31/2021
-
09:28 AM Bug #18267 (Closed): Argument forwarding requires parenthesis on method definitions
- Applied in changeset commit:git|13a9597c7ca83fced5738e9345660ae6aef87eb7.
----------
Argument forwarding definition ... -
03:53 AM Feature #18272 (Third Party's Issue): Please replace unsafe SHA1 with another digest algorithm
10/30/2021
-
10:13 PM Bug #18277: buffer error (Zlib::BufError) in Zlib::Deflate#deflate when using MJIT
- Indeed, it looks related, thanks.
I did a quick google search before but didn't find it.
The advantage of this repr... -
07:54 PM Bug #18277: buffer error (Zlib::BufError) in Zlib::Deflate#deflate when using MJIT
- I believe it's a duplicate of [Bug #18058]
-
01:28 PM Bug #18277: buffer error (Zlib::BufError) in Zlib::Deflate#deflate when using MJIT
- I also tried with latest master as of today:
`ruby 3.1.0dev (2021-10-30T10:24:41Z master a46c220320) +JIT [x86_64-li... -
01:25 PM Bug #18277 (Closed): buffer error (Zlib::BufError) in Zlib::Deflate#deflate when using MJIT
- To repro:
```
$ git clone https://github.com/Shopify/yjit-bench.git
$ cd yjit-bench
$ ruby --jit -I./harness benc... -
05:00 PM Feature #18279 (Closed): ENV.merge! support multiple arguments as Hash.merge!
- I give a useful example for this.
```rb
require 'yaml'
env_files = ['config.yml', 'config.local']
envs = env_fi... -
04:44 PM Bug #18278 (Third Party's Issue): SegFault on exit from gtk3 app
- According to the log, it is very likely to be a problem with gtk3. Could you contact on the author of the gem?
I g... -
04:14 PM Bug #18278 (Third Party's Issue): SegFault on exit from gtk3 app
- I try to implement my gtk3-based app to organize my books/music/etc.
After adding the autocompletion feature the app... -
01:16 AM Bug #14743 (Closed): Some links broken in README
- Applied in changeset commit:git|2898805535104c330e1e5c64c8065a108f1f2895.
----------
Use rdoc-ref to fix a few links...
Also available in: Atom