| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/prism/commit/7a0af49997
|
|
https://github.com/ruby/prism/commit/5dd36b979e
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11765
|
|
(https://github.com/ruby/reline/pull/747)
https://github.com/ruby/reline/commit/7534f7f92a
|
|
prepended to singleton class
To simplify the implementation, this makes Object#singleton_method
call the same method called by Object#method (rb_obj_method), then
check that the returned Method is defined before the superclass of the
object's singleton class. To keep the same error messages, it rescues
exceptions raised by rb_obj_method, and then raises its own exception.
Fixes [Bug #20620]
Notes:
Merged: https://github.com/ruby/ruby/pull/11605
|
|
Notes:
Merged-By: ioquatix <samuel@codeotaku.com>
|
|
(https://github.com/ruby/rdoc/pull/1184)
https://github.com/ruby/rdoc/commit/7b68545094
|
|
(https://github.com/ruby/reline/pull/753)
https://github.com/ruby/reline/commit/9230fe162d
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/10924
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/10924
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/10924
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/10924
|
|
`PTY.spawn` with a block detaches the spawned process and leaves it
running in background even after exiting the given block. It is the
responsibility of the caller to clean up the yielded IOs and PID.
https://github.com/ruby/ruby/actions/runs/11148759246/job/30986064044#step:13:950
```
Leaked file descriptor: Reline::Test#test_tty_amibuous_width: 9 : #<File:/dev/pts/0>
Leaked file descriptor: Reline::Test#test_tty_amibuous_width: 10 : #<File:/dev/pts/0>
Leaked file descriptor: Reline::Test#test_tty_amibuous_width: 11 : #<File:/dev/pts/1>
Leaked file descriptor: Reline::Test#test_tty_amibuous_width: 12 : #<File:/dev/pts/1>
Leaked file descriptor: Reline::Test#test_tty_amibuous_width: 13 : #<File:/dev/pts/2>
Leaked file descriptor: Reline::Test#test_tty_amibuous_width: 14 : #<File:/dev/pts/2>
```
https://github.com/ruby/reline/commit/f9f90da9e4
|
|
(https://github.com/ruby/reline/pull/748)
https://github.com/ruby/reline/commit/bf0f8fa333
|
|
(https://github.com/ruby/reline/pull/750)
https://github.com/ruby/reline/commit/dd4a654e5d
|
|
https://github.com/ruby/prism/commit/aee2de91a3
|
|
https://github.com/ruby/prism/commit/ab9d80987a
|
|
clearing results from all sources
https://github.com/rubygems/rubygems/commit/0549ddbcc5
|
|
It's for avoiding calling release on exit via GC. If it's happen, Ruby
will be crashed because Fiddle::MemoryView's finalizer may refer other
Ruby object. In exit phrase, the referred Ruby object may be already
freed.
https://github.com/ruby/fiddle/commit/02915f13de
|
|
https://github.com/ruby/fiddle/commit/0bfcd02bef
|
|
https://github.com/rubygems/rubygems/commit/517e9a8669
|
|
https://github.com/rubygems/rubygems/commit/0a75590ac9
|
|
(https://github.com/ruby/irb/pull/1007)
In debug command, IRB's context was using wrong binding.
Some code colorization, command detection failed because binding.local_variable returned wrong value.
https://github.com/ruby/irb/commit/68f718de21
|
|
https://github.com/ruby/prism/commit/ccc746f918
|
|
(https://github.com/ruby/reline/pull/751)
https://github.com/ruby/reline/commit/e9d4b37e34
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11753
|
|
https://github.com/ruby/prism/commit/498dd922d4
|
|
Reject argument forwarding in lambda:
- without parentheses
- after optional argument(s)
Notes:
Merged: https://github.com/ruby/ruby/pull/11751
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11738
|
|
|
|
This caused an issue when `defined?` was in the `if` condition. Its
instructions weren't appended to the instruction sequence even though it was compiled
if a compile-time known logical short-circuit happened before the `defined?`. The catch table
entry (`defined?` compilation produces a catch table entry) was still on the iseq even though the
instructions weren't there. This caused faulty exception handling in the method.
The solution is to no add the catch table entry for `defined?` after a compile-time known logical
short circuit.
This shouldn't touch much code, it's only for cases like the following,
which can occur during debugging:
if false && defined?(Some::CONSTANT)
"more code..."
end
Fixes [Bug #20501]
Notes:
Merged: https://github.com/ruby/ruby/pull/11554
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11741
|
|
https://github.com/ruby/prism/commit/fd58d6a9ea
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11735
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11673
|
|
This could happen when a regular gem shadows a default gem.
https://github.com/rubygems/rubygems/commit/9ef70dd1f7
|
|
`Gem::Specification.reset` warning
https://github.com/rubygems/rubygems/commit/e6e3db821f
|
|
https://github.com/rubygems/rubygems/commit/6e0456583b
|
|
helpful.
https://github.com/rubygems/rubygems/commit/e7d6b92e31
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11716
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11702
|
|
|
|
necessary for gems with executables
https://github.com/rubygems/rubygems/commit/2fe0f452a2
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11701
|
|
https://github.com/ruby/prism/commit/976a3cd0a5
|
|
https://github.com/ruby/prism/commit/988ac82187
|
|
https://github.com/ruby/prism/commit/509ff88e92
|
|
https://github.com/ruby/prism/commit/b624e09cc6
|
|
should skip with macOS 15.0
|