| Age | Commit message (Collapse) | Author |
|---|
|
|
|
https://github.com/ruby/prism/commit/72518f5716
|
|
https://github.com/ruby/prism/commit/ab43b3ab66
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/ruby/prism/commit/178d4f66fd
|
|
https://github.com/ruby/prism/commit/863197629c
|
|
https://github.com/ruby/prism/commit/57d5c9be2c
|
|
`--destdir` is given
This was only working for gems also installed in the default gem home.
https://github.com/rubygems/rubygems/commit/47df02dbd9
|
|
https://github.com/rubygems/rubygems/commit/7f0706a897
|
|
Tests have two copies of b-2 installed, one in default home and another
in user home. But only the one in default home was visible because of
not reloading paths. The user install test was working by chance.
https://github.com/rubygems/rubygems/commit/667537a08f
|
|
|
|
> leaving the files after gem rebuild was intentional, for local
> inspection, but the test suite should be made to clean up after
> itself independently of that.
https://github.com/rubygems/rubygems/pull/4913#issuecomment-2081710691
https://github.com/rubygems/rubygems/commit/185a2091fb
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/ruby/prism/commit/dd532ded95
|
|
It is saved in `setup` and restored in `teardown`.
https://github.com/rubygems/rubygems/commit/880c5de667
|
|
passed an outbuf
This accounts for a significant number of string allocations when reading rubygems, but we can avoid that in many places by only copying into the outbuf when present
https://github.com/ruby/zlib/commit/d25ef406c1
|
|
When `gem uninstall <gem> --install-dir <dir>` is run, if the version
removed had a plugin, and that same version happened to also be
installed globally, then the plugin stub would fail to be removed.
https://github.com/rubygems/rubygems/commit/4e2fa0be77
|
|
This class handles all logic to handle the list of specifications, given
a set of GEM_PATH directories. Makes `Gem::Specification` has less
responsibilities and will help with fixing some bugs next.
https://github.com/rubygems/rubygems/commit/df280dbbed
|
|
https://github.com/rubygems/rubygems/commit/b545daa95d
|
|
If we move test directory removal to the very end, I think we should not
leak anything.
https://github.com/rubygems/rubygems/commit/fb3d8944b5
|
|
Before the change `C.keys` returned keys captured in some previous test case that by chance captured `nil` value what made this test passed successfully. Now it returns keys captured in this test case.
|
|
(https://github.com/ruby/reline/pull/701)
* Refactor send
* Implement the undo command
* Fix @past_lines initialization
* Improve assertion
* Hide to save buffer in insert_pasted_text
* Replace @using_delete_command with @undoing
* Refactor `@past_lines`
https://github.com/ruby/reline/commit/4ab72f9cbd
|
|
https://github.com/rubygems/rubygems/commit/716666f65f
|
|
The plugin loader from `@gem_home` was removed during uninstallation.
However, this could leave behind the plugins for `--user-install`
installed gems.
Use `Gem::Specifictaions#base_dir` instead. This ensures that the plugin
loader for associated .gemspec is uninstalled.
https://github.com/rubygems/rubygems/commit/6047f78210
|
|
Instead of unit testing the `remove_plugins` method, test the whole
removal process.
https://github.com/rubygems/rubygems/commit/bfdc60af98
|
|
|
|
|
|
Prohibit setting instance variables of existing classes and modules
via link.
|
|
|
|
https://github.com/ruby/irb/commit/7d60349499
|
|
|
|
(https://github.com/ruby/reline/pull/703)
https://github.com/ruby/reline/commit/21891c47c4
|
|
|
|
https://github.com/ruby/prism/commit/826657232e
|
|
|
|
https://github.com/ruby/prism/commit/b5e47f5c42
|
|
values
(https://github.com/ruby/irb/pull/953)
Currently, users can only find out that they have set a wrong value
for IRB configs when the value is used, with opaque error messages like
"comparison of Integer with true failed (TypeError)".
This commit adds a new initialization step to validate the values of
some IRB configs, so that users can find out about the wrong values
during the initialization of IRB.
https://github.com/ruby/irb/commit/af8ef2948b
|
|
|
|
|
|
The test assumes `:foo` is a static symbol, but that is only true
if a literal `:foo` was parsed before `"foo".to_sym` was evaled:
```ruby
require 'objspace'
foo_sym = "foo".to_sym
puts ObjectSpace.dump(eval(":foo"))
```
```
{"address":"0x100fb46d0", "type":"SYMBOL", "shape_id":10, "slot_size":40, "class":"0x100d3e9c8", "frozen":true, "bytesize":3, "value":"foo", "memsize":40, "flags":{"wb_protected":true, "marking":true, "marked":true}}
```
|
