[#107008] [Ruby master Bug#18465] Make `IO#write` atomic. — "ioquatix (Samuel Williams)" <noreply@...>
Issue #18465 has been reported by ioquatix (Samuel Williams).
16 messages
2022/01/09
[#107150] [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically — "ko1 (Koichi Sasada)" <noreply@...>
Issue #18494 has been updated by ko1 (Koichi Sasada).
4 messages
2022/01/17
[#107170] Re: [Ruby master Feature#18494] [RFC] ENV["RUBY_GC_..."]= changes GC parameters dynamically
— Eric Wong <normalperson@...>
2022/01/17
> https://bugs.ruby-lang.org/issues/18494
[#107302] [Ruby master Bug#18553] Memory leak on compiling method call with kwargs — "ibylich (Ilya Bylich)" <noreply@...>
Issue #18553 has been reported by ibylich (Ilya Bylich).
4 messages
2022/01/27
[#107346] [Ruby master Misc#18557] DevMeeting-2022-02-17 — "mame (Yusuke Endoh)" <noreply@...>
Issue #18557 has been reported by mame (Yusuke Endoh).
18 messages
2022/01/29
[ruby-core:106993] [Ruby master Bug#18389] `binding.irb` can fail in some classes that implement `context` and `print` methods.
From:
"jeremyevans0 (Jeremy Evans)" <noreply@...>
Date:
2022-01-07 00:39:27 UTC
List:
ruby-core #106993
Issue #18389 has been updated by jeremyevans0 (Jeremy Evans).
I've submitted a pull request to fix this error: https://github.com/ruby/irb/pull/325
----------------------------------------
Bug #18389: `binding.irb` can fail in some classes that implement `context` and `print` methods.
https://bugs.ruby-lang.org/issues/18389#change-95824
* Author: ioquatix (Samuel Williams)
* Status: Open
* Priority: Normal
* Assignee: aycabta (aycabta .)
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
```ruby
class Foo
def boop
binding.irb
end
def context
end
def print
end
end
Foo.new.boop
```
It fails with:
```
> ruby ./test.rb
From: ./test.rb @ line 3 :
1: class Foo
2: def boop
=> 3: binding.irb
4: end
5:
6: def context
7: end
8:
./test.rb:9:in `print': wrong number of arguments (given 1, expected 0) (ArgumentError)
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb/extend-command.rb:238:in `install_alias_method'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb/extend-command.rb:252:in `block in extend_object'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb/extend-command.rb:251:in `each'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb/extend-command.rb:251:in `extend_object'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb.rb:466:in `extend'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb.rb:466:in `initialize'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb.rb:959:in `new'
from /Users/samuel/.gem/ruby/3.0.3/gems/irb-1.3.7/lib/irb.rb:959:in `irb'
from <internal:prelude>:5:in `irb'
from ./test.rb:3:in `boop'
from ./test.rb:13:in `<main>'
```
I suggest that `binding.irb` should be a little bit less invasive to avoid these kinds of issues.
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>