| Age | Commit message (Collapse) | Author |
|---|
|
(https://github.com/ruby/erb/pull/94)
This commit updates the Ruby version to follow the commit in Ruby master branch.
https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523
https://github.com/ruby/erb/commit/a5d42484e4
|
|
|
|
https://github.com/ruby/yaml/commit/388cd27291
|
|
https://github.com/ruby/weakref/commit/cccde64080
|
|
https://github.com/ruby/tempfile/commit/475d719e4d
|
|
Suppress documentation for internals
https://github.com/ruby/singleton/commit/4ac0cc497d
|
|
https://github.com/ruby/rubygems/commit/9b169c700f
|
|
https://github.com/ruby/prettyprint/commit/3a43a4bbf6
|
|
https://github.com/ruby/pp/commit/e1f39cb39c
|
|
https://github.com/ruby/open3/commit/e6d09a6aa8
|
|
https://github.com/ruby/open-uri/commit/1ccc576e9a
|
|
https://github.com/ruby/forwardable/commit/909986fee9
|
|
https://github.com/ruby/find/commit/01232ad51a
|
|
https://github.com/ruby/erb/commit/332e200060
|
|
https://github.com/ruby/delegate/commit/020a6cfe4b
|
|
I would like to start making some of the methods in Gem::Package
private so that we can refactor them better. Right now we have many
methods that are public, and since they are public we can't refactor
them. Historically, I think "private" methods have just been tagged
with :nodoc:, but I would like to be more strict about our APIs
https://github.com/ruby/rubygems/commit/fb352e9176
|
|
Use `<tt>` instead of `+` that cannot enclose punctuations.
https://github.com/ruby/rubygems/commit/f84035c0b6
|
|
It was bound to `module Gem`, instead of `module Deprecate`.
https://github.com/ruby/rubygems/commit/da29f74ba1
|
|
https://github.com/ruby/cgi/commit/ebd04d1eb1
|
|
https://github.com/ruby/rubygems/commit/2078f3d351
|
|
https://github.com/ruby/net-http/commit/b7c586985a
|
|
For open_timeout support detection, the previous implementation relied
on an ArgumentError being raised and then rescued. In Ruby, rescue is a
rather expensive operation and should be avoided when possible.
This patch reduces the number of begin-rescues by remembering if the
TCPSocket implementation supports open_timeout.
https://github.com/ruby/net-http/commit/06d982f3a1
|
|
https://github.com/ruby/net-http/commit/09bf573dd5
|
|
when available
This patch replaces the implementation of #open_timeout from Timeout.timeout from the builtin timeout in TCPSocket.open, which was introduced in Ruby 3.5 (https://bugs.ruby-lang.org/issues/21347).
The builtin timeout in TCPSocket.open is better in several ways than Timeout.timeout. It does not rely on a separate Ruby Thread for monitoring Timeout (which is what the timeout library internally does).
Furthermore, it is compatible with Ractors, as opposed to Timeout.timeout (it internally uses Thread::Mutex which can not be used in non-main Ractors).
This change allows the following code to work.
require 'net/http'
Ractor.new {
uri = URI('http://example.com/')
http = Net::HTTP.new(uri.host, uri.port)
http.open_timeout = 1
http.get(uri.path)
}.value
In Ruby <3.5 environments where `TCPSocket.open` does not have the `open_timeout` option, I have kept the behavior unchanged. net/http will use `Timeout.timeout { TCPSocket.open }`.
https://github.com/ruby/net-http/commit/728eb8fc42
|
|
https://github.com/ruby/resolv/commit/7c5bfe7acd
|
|
This reverts commit af610e107c3a7515228843eb6b1c5978f2ee2685.
Reverted by a mistake.
|
|
This reverts commit 155cdce539a95b510a80a19e3840cde6b293cd4d.
|
|
https://github.com/ruby/net-http/commit/58685b78ab
|
|
https://github.com/ruby/resolv/commit/d8b8d36f63
|
|
And Use Win32::Resolv instead of a constant `WINDOWS`.
https://github.com/ruby/resolv/commit/b2c775cd80
|
|
https://github.com/ruby/resolv/commit/60bf151a1d
|
|
https://github.com/ruby/ipaddr/commit/cb9f561883
|
|
https://github.com/ruby/ipaddr/commit/ada04589fe
|
|
https://github.com/ruby/net-http/commit/e4d80bd609
|
|
https://github.com/ruby/net-http/commit/89e1ecb556
|
|
https://github.com/ruby/net-protocol/commit/6c5734dc1e
|
|
https://github.com/ruby/net-protocol/commit/8286341e8c
|
|
https://github.com/ruby/optparse/commit/0125cb4918
|
|
See https://github.com/ruby/ruby/commit/6d81969b475262aba251e99b518181bdf7c5a523
It leaves the old variant around. RuboCop for examples accesses `Prism::Translation::Parser35`
to test against ruby-head. For now I left these simply as an alias
https://github.com/ruby/prism/commit/d0a823f045
|
|
https://github.com/ruby/rubygems/commit/6c161b253d
|
|
https://github.com/ruby/rubygems/commit/6e965b7872
|
|
https://github.com/ruby/rubygems/commit/79ba4a537d
|
|
|
|
|
|
execution tag
(https://github.com/ruby/erb/pull/92)
These were the wrong way around.
https://github.com/ruby/erb/commit/50a5cd76fe
|
|
https://github.com/ruby/uri/commit/f1b05c89ab
|
|
Effectively reverts commit https://github.com/ruby/uri/commit/788274b180d6 and
https://github.com/ruby/uri/commit/0abac721d8fe.
EMAIL_REGEXP was mostly drawn from WHATWG HTML LS. This spec states that
it intentionally violates RFC 5322 to provide a practical regex for
validation.
> This requirement is a willful violation of RFC 5322, which defines a
> syntax for email addresses that is simultaneously too strict (before the
> "@" character), too vague (after the "@" character), and too lax
> (allowing comments, whitespace characters, and quoted strings in manners
> unfamiliar to most users) to be of practical use here.
The allowing of consecutive dot s(`a..a@`) and leading/trailing dots
(`.a@`, `a.@`) is not the only derivation from RFC 5322. If a truly RFC
5322-compliant regexp is needed, tt should be organized under a
different name, since too much departure from the original EMAIL_REGEXP
must be introduced.
https://github.com/ruby/uri/commit/c551d7020b
|
|
This reverts commit 2c2eaa3103e5cf1cbfc2b16d9db975a9b8a0399a.
|
|
I would like to use the tar implementation inside a Ractor, but two of
the constants are not frozen. This patch freezes the constants so we
can use it in a Ractor.
https://github.com/ruby/rubygems/commit/0ff4790f4c
|
|
building gems
In general, rubygems should provide mechanism and not policy.
Pessimistic versioning is not universally better, and in many
cases, it can cause more problems than it solves. Rubygems should
not be warning against open-ended versioning when building gems.
The majority of the default gems with dependencies do not use
pessimistic versioning, which indicates that Ruby itself
recognizes that open-ended versioning is generally better.
In some cases, depending on a prerelease gem is the only choice
other than not releasing a gem. If you are building an extension
gem for a feature in a prerelease version of another gem, then
depending on the prerelease version is the only way to ensure
a compatible dependency is installed.
https://github.com/ruby/rubygems/commit/beba8dd065
|
