| Age | Commit message (Collapse) | Author |
|
(https://github.com/ruby/reline/pull/668)
https://github.com/ruby/reline/commit/91b030caa4
|
|
https://github.com/ruby/prism/commit/e2147cddd8
|
|
because clear(C-l) is not a signal
(https://github.com/ruby/reline/pull/646)
https://github.com/ruby/reline/commit/3debb0ae2f
|
|
rendering
(https://github.com/ruby/reline/pull/648)
https://github.com/ruby/reline/commit/9c51c577ca
|
|
https://github.com/rubygems/rubygems/commit/ee0bef2786
|
|
https://github.com/rubygems/rubygems/commit/b2a88983db
|
|
|
|
|
|
Introduce a new mkmf option `--target-rbconfig` to specify the RbConfig
file for the deployment target platform. This option is useful for
cross-compiling Ruby extensions without faking the global top-level
`RbConfig` constant.
|
|
|
|
(https://github.com/ruby/reline/pull/647)
* Refactor completion: split autocompletion and tabcompletion logic and state
* Move completion candidate listup logic from dialog proc to LineEditor
https://github.com/ruby/reline/commit/c3c09ac9c2
|
|
(https://github.com/ruby/reline/pull/613)
https://github.com/ruby/reline/commit/a622704f62
|
|
everything
https://github.com/rubygems/rubygems/commit/1ea44b3749
|
|
https://github.com/rubygems/rubygems/commit/7b5cc51a96
|
|
https://github.com/rubygems/rubygems/commit/6ca192649f
|
|
We just need to filter versions belonging to the range, but don't need
anything else.
https://github.com/rubygems/rubygems/commit/8355a225d7
|
|
https://github.com/rubygems/rubygems/commit/bb5727934c
|
|
So that we don't need to reverse the Array.
https://github.com/rubygems/rubygems/commit/aeea5e2e00
|
|
https://github.com/rubygems/rubygems/commit/ac24a68486
|
|
We do that when first caching versions, and then it's no longer
necessary.
https://github.com/rubygems/rubygems/commit/ede15847db
|
|
https://github.com/rubygems/rubygems/commit/13294528c4
|
|
And also so that it matches the method used by main PubGrub sample
resolver class.
https://github.com/rubygems/rubygems/commit/0e612361b8
|
|
https://github.com/rubygems/rubygems/commit/0ddf25e5aa
|
|
https://github.com/rubygems/rubygems/commit/3c4e3fadc9
|
|
https://github.com/rubygems/rubygems/commit/4ebf6ee5ac
|
|
GemspecHelpers.
https://github.com/rubygems/rubygems/commit/2f80a595c4
|
|
https://github.com/rubygems/rubygems/commit/701550f9dd
|
|
suggest passing --diff.
https://github.com/rubygems/rubygems/commit/7caadd182c
|
|
doesn't match.
https://github.com/rubygems/rubygems/commit/a691170dc7
|
|
https://github.com/rubygems/rubygems/commit/8644ce7193
|
|
https://github.com/rubygems/rubygems/commit/4446389f2e
|
|
working directory.
https://github.com/rubygems/rubygems/commit/f2e4e5b56f
|
|
https://github.com/rubygems/rubygems/commit/3e9545193a
|
|
https://github.com/rubygems/rubygems/commit/3b88553d0d
|
|
https://github.com/rubygems/rubygems/commit/6d661573f0
|
|
https://github.com/ruby/prism/commit/2068e3c30a
|
|
Most of the calls to `FormatError.new` pass `@gem` for the second argument, which has a `path` method.
But in one case—on package.rb:691 in `verify_gz`, the `source` argument is a `String`.
So if there's ever a GZip decode error when attempting to read the contents of the `data.tar.gz` file, instead of reporting the underlying GZip error (which might be something like "unexpected end of file"), we would report instead a NoMethodError coming from package.rb
```
Exception while verifying sorbet-0.5.11301.gem
ERROR: While executing gem ... (NoMethodError)
undefined method `path' for "data.tar.gz":String
@path = source.path
^^^^^
```
There are two ways to fix this:
1. Make `FormatError#initialize` aware of the fact that `source` might sometimes be a `String`
2. Make the call to `FormatError.new` in `verify_gz` pass `@gem` instead of `entry.full_name`.
I've chosen 1 because I think it's more useful to see "unexpected end of file in data.tar.gz" instead of "unexpected end of file in sorbet-0.5.11301.gem." The end of file **is actually** in data.tar.gz, not in the gem file itself, which was decoded successfully.
|
|
We use the following site for that now:
* https://tools.ietf.org/ or http
* https://datatracker.ietf.org or http
Today, IETF said the official site of RFC is www.rfc-editor.org.
FYI: https://authors.ietf.org/en/references-in-rfcxml
I replaced them to www.rfc-editor.org.
|
|
Also bring the man page up to date.
https://github.com/rubygems/rubygems/commit/a849bd6947
|
|
|
|
https://github.com/ruby/prism/commit/50372fee5c
|
|
https://github.com/ruby/irb/commit/2057248e40
|
|
not properly compared
They were delegating their `#hash` value to a class not overriding that
method, and so were returning inconsistent results.
https://github.com/rubygems/rubygems/commit/723e4ee0fc
|
|
Ensure only one source type is specified, and ensure options that
are only relevant to git sources are only specified with git.
https://github.com/rubygems/rubygems/commit/58b043215e
|
|
Fixes https://github.com/ruby/prism/pull/2617.
There was an issue with the lexer as follows.
The following are valid regexp options:
```console
$ bundle exec ruby -Ilib -rprism -ve 'p Prism.lex("/x/io").value.map {|token| token[0].type }'
ruby 3.3.0 (2023-12-25 revision https://github.com/ruby/prism/commit/5124f9ac75) [x86_64-darwin22]
[:REGEXP_BEGIN, :STRING_CONTENT, :REGEXP_END, :EOF]
```
The following are invalid regexp options. Unnecessary the `IDENTIFIER` token is appearing:
```console
$ bundle exec ruby -Ilib -rprism -ve 'p Prism.lex("/x/az").value.map {|token| token[0].type }'
ruby 3.3.0 (2023-12-25 revision https://github.com/ruby/prism/commit/5124f9ac75) [x86_64-darwin22]
[:REGEXP_BEGIN, :STRING_CONTENT, :REGEXP_END, :IDENTIFIER, :EOF]
```
As a behavior of Ruby, when given `A` to `Z` and `a` to `z`, they act as invalid regexp options. e.g.,
```console
$ ruby -e '/regexp/az'
-e:1: unknown regexp options - az
/regexp/az
-e: compile error (SyntaxError)
```
Thus, it should probably not be construed as `IDENTIFIER` token.
Therefore, `pm_byte_table` has been adapted to accept those invalid regexp option values.
Whether it is a valid regexp option or not is checked by `pm_regular_expression_flags_create`.
For invalid regexp options, `PM_ERR_REGEXP_UNKNOWN_OPTIONS` is added to diagnostics.
https://github.com/ruby/prism/commit/d2a6096fcf
|
|
for RubyParser translation
https://github.com/ruby/prism/commit/a37169621a
|
|
(https://github.com/ruby/reline/pull/664)
https://github.com/ruby/reline/commit/1d6569600c
|
|
(https://github.com/ruby/irb/pull/911)
* Cache RDoc::RI::Driver.new to improve performance and to avoid flaky test
* Insert sleep to fix flaky rendering test that renders document dialog
https://github.com/ruby/irb/commit/da84e6cb56
|
|
(https://github.com/ruby/reline/pull/665)
The pasting tests hadn't been working since as early as v0.2.0. Since
what it tried to cover is already gone for such a long time, I think it's
better to write new ones if needed then to keep them around.
And since these tests are gone, the helper methods for just them are also gone.
https://github.com/ruby/reline/commit/0eedf0e4a0
|
|
Followup: https://github.com/ruby/ruby/pull/10347
This avoid directly referencing bootsnap and zeitwerk, and also
handle other gems that may decorate `require`.
|