Age | Commit message (Collapse) | Author |
|
It's a sources specific concern, so keep it there. It allows to simplify
the code quite a lot.
https://github.com/rubygems/rubygems/commit/639f0b72f4
|
|
lockfile
https://github.com/rubygems/rubygems/commit/4e048bc255
|
|
https://github.com/rubygems/rubygems/commit/5074c58ffb
|
|
https://github.com/rubygems/rubygems/commit/dc7c9f029a
|
|
https://github.com/rubygems/rubygems/commit/508ed917a5
|
|
This was an offramp for generated etags to allow existing caches
to be served until people could upgrade. It has been about 6 months
since the transitional version was released, so we can remove this
transitional code now.
https://github.com/rubygems/rubygems/commit/4ec8cfe611
|
|
https://github.com/ruby/rdoc/commit/a667e616e1
|
|
https://github.com/ruby/prism/commit/53bbcfe513
|
|
https://github.com/rubygems/rubygems/commit/022eb473f8
|
|
https://github.com/rubygems/rubygems/commit/592a2fcd54
|
|
get_screen_size. Closes https://github.com/ruby/reline/pull/690
(https://github.com/ruby/reline/pull/702)
* Catches exceptions Errno::ENODEV and Errno::EBADF in get_screen_size. Closes https://github.com/ruby/reline/pull/690
* Just catching Errno::ENOTTY and Errno::ENODEV
https://github.com/ruby/reline/commit/a5b5298e4a
|
|
https://github.com/ruby/prism/commit/79cec4be22
|
|
https://github.com/ruby/prism/commit/77bf9038a2
|
|
This eliminates the subnode on RationalNode and replaces it with two
integer fields, which represent the ratio for the rational. It also
reduces those two integers if they both fit into 32 bits.
Importantly, this PR does not implement bignum reduction. That's something
I'd like to consider for the future, but it's simple enough for now to
leave them unreduced, which makes it more useful than it used to be.
https://github.com/ruby/prism/commit/86e06c7068
|
|
(https://github.com/ruby/irb/pull/956)
When a syntax error includes multiple error messages, we want to
check for unrecoverable messages first so that we do not
accidentally match a recoverable error later in the message.
https://github.com/ruby/irb/commit/2f42b2360d
|
|
This gem contains no executables.
https://github.com/ruby/find/commit/7bd452155e
|
|
`--destdir` is given
This was only working for gems also installed in the default gem home.
https://github.com/rubygems/rubygems/commit/47df02dbd9
|
|
So that it can also be delegated to `Gem::SpecificationRecord`.
https://github.com/rubygems/rubygems/commit/1407807a99
|
|
https://github.com/rubygems/rubygems/commit/7f0706a897
|
|
https://github.com/rubygems/rubygems/commit/5fbe5e43d6
|
|
If `cache_all_platforms` setting is enabled, the secondary source was
no longer considering cached gems.
That means that if the remote secondary source has removed its gems,
then this was now resulting in an error while before the previously
cached gem from the source would still be used.
This commit restores previous behavior.
https://github.com/rubygems/rubygems/commit/2d2cd00255
|
|
https://github.com/rubygems/rubygems/commit/6166e4bce1
|
|
https://github.com/rubygems/rubygems/commit/5d03a346ab
|
|
https://github.com/rubygems/rubygems/commit/535c83d5be
|
|
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/8c9807092c
|
|
Other analog methods are documented, so document this one too.
https://github.com/rubygems/rubygems/commit/76da34d44d
|
|
I don't think this method is any worse than others, let's only document
what it does.
https://github.com/rubygems/rubygems/commit/dec722187f
|
|
https://github.com/rubygems/rubygems/commit/7b71965a70
|
|
(https://github.com/ruby/reline/pull/704)
https://github.com/ruby/reline/commit/b9b3d392ff
|
|
(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
|
|
I'm not sure why but this particular change seems to have introduced
some flaky test failures. So I'll revert it.
https://github.com/rubygems/rubygems/commit/668488014b
|
|
https://github.com/rubygems/rubygems/commit/de4650f629
|
|
https://github.com/rubygems/rubygems/commit/8c8aaecc48
|
|
https://github.com/ruby/prism/commit/d4eb13e703
|
|
Resolves https://github.com/ruby/prism/pull/2803.
This PR adds error handling for missing `parser` gem in `Prism::Translation`.
The `parser` gem is a required runtime dependency when using `Prism::Translation::Parser`.
But it is not required for other uses of Prism. To avoid unnecessary dependencies,
it is not added as a `runtime_dependency` in the prism.gemspec. Instead, if the dependency is missing,
instructions are given to add it to Gemfile.
## Before
```console
$ bundle exec ruby -e 'require "prism"; require "prism/translation/parser33"'
/Users/koic/.rbenv/versions/3.3.1/lib/ruby/3.3.0/bundled_gems.rb:74:in `require': cannot load such file -- parser (LoadError)
from /Users/koic/.rbenv/versions/3.3.1/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'
from /Users/koic/src/github.com/ruby/prism/lib/prism/translation/parser.rb:3:in `<top (required)>'
from /Users/koic/.rbenv/versions/3.3.1/lib/ruby/3.3.0/bundled_gems.rb:74:in `require'
from /Users/koic/.rbenv/versions/3.3.1/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'
from /Users/koic/src/github.com/ruby/prism/lib/prism/translation/parser33.rb:6:in `<module:Translation>'
from /Users/koic/src/github.com/ruby/prism/lib/prism/translation/parser33.rb:4:in `<module:Prism>'
from /Users/koic/src/github.com/ruby/prism/lib/prism/translation/parser33.rb:3:in `<top (required)>'
from /Users/koic/.rbenv/versions/3.3.1/lib/ruby/3.3.0/bundled_gems.rb:74:in `require'
from /Users/koic/.rbenv/versions/3.3.1/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'
from -e:1:in `<main>'
```
## After
```console
$ bundle exec ruby -e 'require "prism"; require "prism/translation/parser33"'
Error: Unable to load parser. Add `gem "parser"` to your Gemfile.
```
https://github.com/ruby/prism/commit/4880aec22d
|
|
Having the @newline instance variable in every node adds up, and
since it is so rarely used, we only want to add it when necessary.
Moving this into an autoloaded file and moving the instance variable
out of the default initializers reduces allocated memory because the
nodes are now smaller and some fit into the compact list. On my
machine, I'm seeing about an 8% drop.
https://github.com/ruby/prism/commit/eea92c07d2
|
|
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
|
|
If one upgrades the default copy of Bundler through `gem update
--system`, and then reinstalls Ruby without removing the previous copy.
Then the new installation will have a correct default bundler gemspec,
but a higher copy installed in site_dir.
This causes a crash when running Bundler and prints the bug report
template.
This could probably be fixed in Ruby install script, by removing any
previous Bundler default copies, but if the problem is already there, I
think it's best to print a proper user error.
https://github.com/rubygems/rubygems/commit/ada6de765d
|
|
We should make sure Bundler does not trigger RubyGems require logic for
gem activation until it had the chance to register its own monkeypatches
to RubyGems.
https://github.com/rubygems/rubygems/commit/fbd2ff86b9
|
|
https://github.com/rubygems/rubygems/commit/07022e3f2f
|
|
(https://github.com/ruby/reline/pull/703)
https://github.com/ruby/reline/commit/21891c47c4
|
|
|
|
https://github.com/ruby/prism/commit/b5e47f5c42
|
|
https://github.com/ruby/prism/commit/15bf727881
|
|
https://github.com/ruby/prism/commit/ee73ad757f
|
|
https://github.com/ruby/prism/commit/fa6fe9be84
|
|
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
|