| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
https://github.com/ruby/digest/commit/16b598d6f2
|
|
Failed build in #70.
Pre-3.0 versions of Ruby didn't support pattern matching, and power_assert warned.
https://github.com/ruby/timeout/commit/983cbf636a
|
|
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/stringio/commit/cf58a203eb
|
|
https://github.com/ruby/cgi/commit/ebd04d1eb1
|
|
https://github.com/ruby/rubygems/commit/2078f3d351
|
|
https://github.com/ruby/stringio/commit/27b2fb2fce
|
|
https://github.com/ruby/net-http/commit/b7c586985a
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Commits](https://github.com/actions/checkout/compare/v4...v5)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: '5'
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
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
|
|
|
|
|
|
It may return sizes that aren't allocatable for arrays and strings.
|
|
It was supposed to update a local branch in case the remote branch was
updated between actions/checkout and the end of tool/sync_default_gems.rb.
Note that this `git pull` didn't exist in the original bin/update-default-gem.sh
https://github.com/ruby/git.ruby-lang.org/commit/d9e9bcc60dcf0dd1cbdc2dd42bc0286439e471aa,
so it was newly introduced at https://github.com/ruby/ruby/commit/3ba5cfd1cb77b61b2b1ad1d03271bc1fe7b71969.
But `git pull --no-ff` failed when master had updates in an unrelated
repository. I think we need to use `git pull --rebase` instead.
This fixes:
* https://github.com/ruby/ruby/actions/runs/19207693793/job/54905403070
* checkout: f08030e9dccf38d9ea5c9505203fe26484dc28d8
* ruby tool/sync_default_gems.rb net-http ec9c70a6fba75a63c128864ef3cb32c883665a33..e4d80bd609f22cad04a2e2c1d54c981bb853c938
* pull: 2bf82c627494e785737037bbaf9a6b98f3c6354c
|
|
rb_gc_impl_shutdown_call_finalizer
https://github.com/ruby/mmtk/commit/1828f6596f
|
|
|
|
Follow-up: https://github.com/ruby/ruby/pull/15116
|
|
|
|
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/win32-registry/commit/8680eedd43
|
|
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
|
