Ruby Issue Tracking System

12/12/2019

05:12 PM Ruby Misc #16408: Ruby docs list incorrect method signatures for PTY::getpty/PTY::spawn

Turns out `IO.pipe` would result in `"bar\n"` instead of `"bar\r\n"` (`PTY.open` results in strings that end in `"\r\n"`). Given the rest of the file's test cases all expect strings that end in `"\r\n"`, I thought that sticking to conven... yarmiganosca (Chris Hoffman)

12/08/2019

06:30 PM Ruby Misc #16408 (Open): Ruby docs list incorrect method signatures for PTY::getpty/PTY::spawn

Ruby documentation says the method signature for `PTY::getpty`/`PTY::spawn` is
```
* PTY.spawn(command_line) { |r, w, pid| ... }
* PTY.spawn(command_line) => [r, w, pid]
* PTY.spawn(command, arguments, ...) { |r, w, pid| ... yarmiganosca (Chris Hoffman)

12/13/2018

05:04 AM Ruby Bug #15410: double-splatted parameters behave differently if one of the keys is an array

I've been informed that this is expected behavior according to the spec, but I don't know how to close my own issues (or even if I can), so feel free to close this. yarmiganosca (Chris Hoffman)

04:33 AM Ruby Bug #15410 (Closed): double-splatted parameters behave differently if one of the keys is an array

~~~
➜ irb
2.5.1 :001 > def thingy(x, **y); [x, y]; end
=> :thingy
2.5.1 :002 > thingy(4, {:x => 5})
=> [4, {:x=>5}]
2.5.1 :003 > thingy(4, {[:x] => 5})
Traceback (most recent call last):
16: from /home/choffman/.rvm/ge... yarmiganosca (Chris Hoffman)

06/26/2018

05:39 AM Ruby Bug #14870 (Closed): Both TracePoint's :call and :c_call filters seem to skip a lot of builtin methods

It looks like a lot of builtin methods (`Array#<<` and `Integer#+`, for example) aren't hooked when using the :call or :c_call filters for TracePoint.
```
➜ irb
:001 > [RUBY_VERSION, RUBY_PATCHLEVEL]
=> ["2.5.1", 57]
:002 > Tr... yarmiganosca (Chris Hoffman)