| Age | Commit message (Collapse) | Author |
|
default_spec_cache_dir
https://github.com/rubygems/rubygems/commit/d2801fcfde
|
|
I'm running into a case in my plugin where matches_current_metadata? is
getting called on a lazy specification, and adding this fixes it
https://github.com/rubygems/rubygems/commit/24f962cb42
|
|
https://github.com/rubygems/rubygems/commit/4691b959ad
|
|
It's possible to repeat parameters in method definitions like so:
```ruby
def foo(_a, _a)
end
```
The compiler needs to know to adjust the local table size to account for
these duplicate names. We'll use the repeated parameter flag to account
for the extra stack space required
https://github.com/ruby/prism/commit/b443cb1f60
Co-Authored-By: Kevin Newton <kddnewton@gmail.com>
Co-Authored-By: Jemma Issroff <jemmaissroff@gmail.com>
|
|
|
|
|
|
https://github.com/ruby/prism/commit/3e36d5eabc
|
|
By providing a 'changelog_uri' in the metadata of the gemspec a
'Changelog' link will be shown on https://rubygems.org/gems/abbrev
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details of this functionality can be found on https://guides.rubygems.org/specification-reference/
https://github.com/ruby/abbrev/commit/9643a03ee8
|
|
|
|
https://github.com/rubygems/rubygems/commit/aa3ae5d245
|
|
(https://github.com/ruby/irb/pull/836)
https://github.com/ruby/irb/commit/73b35bb7f4
|
|
|
|
|
|
Even for singleton class definition such as `class << self` that
shares the same container with the outer scope, its visibility is
separated and set to `public` by default.
https://github.com/ruby/rdoc/commit/baf26363b9
|
|
Each singleton method definition of the form `def recv.method` has
visibility separate from the outer scope and is set to `public` by
default.
https://github.com/ruby/rdoc/commit/810913a7ea
|
|
https://github.com/ruby/net-http/commit/3bf641ca63
|
|
(https://github.com/ruby/irb/pull/835)
* Remove unnecessary code from the exit command's implementation
1. The parameters of `IRB.irb_exit` were never used. But there are some
libraries seem to call it with arguments + it's declared on the top-level
IRB constant. So I changed the params to anonymous splat instead of removing them.
2. `Context#exit` was completely unnecessary as `IRB.irb_exit` doesn't use
the `@irb` instance it passes. And since it's (or should be treated as)
a private method, I simply removed it.
3. The `exit` command doesn't use the status argument it receives at all.
But to avoid raising errors on usages like `exit 1`, I changed the argument to
anonymous splat instead removing it.
* Make exit an actual command
* Update readme
https://github.com/ruby/irb/commit/452b543a65
|
|
(https://github.com/ruby/irb/pull/834)
https://github.com/ruby/irb/commit/eff8d0d46a
|
|
`@locale` is set from `@locale_name` and loaded from `@locale_dir`
after `write_options`, and `RDoc::I18n::Locale` does not seem to
expected to be loaded.
https://github.com/ruby/rdoc/commit/fd610f7023
|
|
Get rid of nested double quotes inside nested interpolations. Also,
remove comments that are no longer needed by the documents.
|
|
If a socket error occurs while performing a streaming download via
the response block provided to transport_request, avoid calling
the response block again as this would result in duplicate data
received by the client.
Fixes https://github.com/ruby/net-http/pull/86
Fixes https://github.com/ruby/net-http/pull/87
Fixes [Bug #11526]
https://github.com/ruby/net-http/commit/114d01b092
Co-authored-by: Jeremy Stanley <jeremy@instructure.com>
|
|
Otherwise, the path could be considered part of the host or port.
This is better than modifying the path to make it absolute when
a host or port is set. We could also raise for invalid paths
when a host or port is set using check_path, but that results
in weird errors, and won't catch issues (such as ftp allowing a
relative path).
Fixes [Bug #19916]
https://github.com/ruby/uri/commit/ac32aa005b
|
|
(https://github.com/ruby/reline/pull/633)
https://github.com/ruby/reline/commit/5b59e48070
|
|
https://github.com/ruby/net-http/commit/21e226c0bc
|
|
request
https://github.com/rubygems/rubygems/commit/d26bcd7551
|
|
https://github.com/ruby/erb/commit/b68bfed6a8
|
|
(https://github.com/ruby/reline/pull/630)
https://github.com/ruby/reline/commit/90155fd0d9
|
|
https://github.com/rubygems/rubygems/commit/7576c21295
|
|
https://github.com/ruby/prism/commit/75d4331f7f
|
|
(https://github.com/ruby/irb/pull/832)
The candidate list for empty input is all methods + all variables +
all constants + all keywords. It's a long list that is not useful.
https://github.com/ruby/irb/commit/812dc2df7b
|
|
Because this is a user-facing change, we also need to deal with the
fact that CRuby 3.3.0 was just released.
In order to support workflows that want to parse exactly as CRuby
parses in a specific version, this PR introduces a new option to
the options struct that is "version". This allows you to specify
that you want "3.3.0" parsing.
I'm not sure if this is the correct solution. Another solution is
to just fork and keep around the old branch for security patches.
Or we could keep around a copy of the source files within this
repository as another directory and only update when necessary.
There are a lot of potential solutions here.
Because this change is so small and the check for it is so minimal,
I've decided to go with this enum. If this ends up entirely
cluttering the codebase with version checks, we'll come up with
another solution. But for now this works, so we're going to go in
this direction for a bit until we determine it's no longer working.
https://github.com/ruby/prism/commit/d8c7e6bd10
|
|
(https://github.com/ruby/irb/pull/831)
https://github.com/ruby/irb/commit/5843616c78
|
|
(https://github.com/ruby/irb/pull/826)
* Fix display_document params in noautocomplete mode
* Fix wrong preposing and target order in display_document
The fixed wrong-ordered value is not used in RegexpCompletor, so this change does not affect the test.
https://github.com/ruby/irb/commit/08208adb5e
|
|
https://github.com/ruby/rdoc/commit/914a6af137
|
|
https://github.com/ruby/securerandom/commit/647e5f0af8
|
|
(https://github.com/ruby/reline/pull/623)
https://github.com/ruby/reline/commit/38e9cb2899
|
|
(https://github.com/ruby/reline/pull/617)
https://github.com/ruby/reline/commit/63deef4ae5
|
|
https://github.com/ruby/securerandom/commit/b587b8c7cb
|
|
|
|
https://github.com/ruby/syntax_suggest/commit/66e1cf0b3e
|
|
|
|
https://github.com/ruby/resolv/commit/5dfdcfb7c7
|
|
https://github.com/ruby/irb/commit/2d5a1afdf5
|
|
IPV4 address is private
Same as #57
https://github.com/ruby/ipaddr/commit/d56acecb80
|
|
Changes introduced by 09edfd4 have broken some exception
messages, and added the address as an unnecessary
suffix in others.
https://github.com/ruby/ipaddr/commit/74a043109c
|
|
`IPAddr.ntop` takes the binary representation of an IP address, whose
length should be 4 or 16 *bytes* (not characters/codepoints).
The current implementation accepts strings in any encoding, but for
some values in non-BINARY encoding, it fails proper length check and
raises an `AddressFamilyError`. Since passing strings in a multibyte
encoding has never worked correctly for years, this patch makes it an
explicit error with an `InvalidAddressError`.
Fixes: https://github.com/ruby/ipaddr/issues/56
https://github.com/ruby/ipaddr/commit/a33fd14d4a
|
|
https://github.com/ruby/securerandom/commit/e8be08901a
|
|
https://github.com/ruby/tempfile/commit/6932d6bc6f
|
|
https://github.com/ruby/csv/commit/0cba3e766d
|
|
https://github.com/ruby/etc/commit/0353d7c8ee
|