| Age | Commit message (Collapse) | Author |
|
Only `RbConfig::MAKEFILE_CONFIG` is actually used.
https://github.com/rubygems/rubygems/commit/b767cc0929
|
|
https://github.com/ruby/fileutils/commit/13ab96439b
|
|
units
* Returning nil from the `content_range` method instead of raising an
error when the unit in the content-range header is not "bytes".
Fix https://bugs.ruby-lang.org/issues/11450
https://github.com/ruby/net-http/commit/0b5030dd86
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
This reverts commit 63546bfc1581d4abec2a0d846106a1c0afc0efa9.
|
|
Probably intended to pass encoding "none".
https://github.com/ruby/racc/commit/65cd26efd8
|
|
* Added a nil check in Net::HTTPHeader#initialize_http_header for keys in the header that do not have any value
* Returning nil from the content_range method instead of raising an error when the unit in the content-range header is not bytes
* Modified initialize_http_header to match trunk
fix [Bug #11450]
fix https://github.com/ruby/ruby/pull/1018
Notes:
Merged-By: nurse <naruse@airemix.jp>
|
|
(https://github.com/ruby/fileutils/pull/88)
https://github.com/ruby/fileutils/commit/ba3ae2430d
|
|
* More on cp_r
https://github.com/ruby/fileutils/commit/82a2b62578
|
|
(https://github.com/ruby/fileutils/pull/86)
* More on paths and lists
https://github.com/ruby/fileutils/commit/c3d92d34f4
|
|
(https://github.com/ruby/fileutils/pull/85)
https://github.com/ruby/fileutils/commit/5f9ef9ddc8
|
|
Treats:
::chown_R
::touch
::commands
::options
::have_option?
::options_of
::collect_method
https://github.com/ruby/fileutils/commit/5df0324f52
|
|
nevans/workaround-linker-script-so"
This reverts commit https://github.com/ruby/reline/commit/4ccf128ffa18, reversing
changes made to https://github.com/ruby/reline/commit/a2651419e9a0.
https://github.com/ruby/reline/commit/51053138a4
|
|
It sent the char to check even to non-tty, e.g., pipe.
This causes `unknown command: "\xE2\x96\xBDstart ` warnings on
ruby's parallel test on Windows, where non-standard FDs cannot be
passed to child processes.
https://github.com/ruby/reline/commit/0d373647fb
|
|
These gemspecs already work most of the times. When they are installed
normally, the require_paths in the gemspec stub line becomes actually
correct, and the incorrect value in the real gemspec is ignored. It only
becomes an issue in standalone mode.
In Ruby 3.2, `Kernel#=~` has been removed, and that means that it
becomes harder for us to gracefully deal with this error in standalone
mode, because it now happens earlier due to calling `Array#=~` for this
invalid gemspec (since require_paths is incorrectly an array of arrays).
The easiest way to fix this is to actually make this just work instead
by automatically fixing the issue when reading the packaged gemspec.
https://github.com/rubygems/rubygems/commit/d3f2fe6d26
|
|
specification
Previously we would instantiate two different packages and extract the
specification from the package twice for each gem installed. We can
reuse the installer for this so that we just need to do it once.
https://github.com/rubygems/rubygems/commit/e454f850b1
|
|
https://github.com/rubygems/rubygems/commit/ba975b3b7f
|
|
https://github.com/rubygems/rubygems/commit/600a9ac658
|
|
This is the explanation of why we do the swapping, not of why we
download the gem.
https://github.com/rubygems/rubygems/commit/1a25eb7e7b
|
|
installer
https://github.com/rubygems/rubygems/commit/796eebfdbf
|
|
https://github.com/rubygems/rubygems/commit/9bd389e1b6
|
|
It's only related to the `bundle cache` command, so it should be checked
there.
https://github.com/rubygems/rubygems/commit/cf749f8ffa
|
|
https://github.com/rubygems/rubygems/commit/285ccbc07e
|
|
https://github.com/rubygems/rubygems/commit/d86fb2c316
|
|
https://github.com/rubygems/rubygems/commit/04e6a5ae31
|
|
These days all these errors are raised as `Gem::Security::Exception` so
there's no need to do any matching on the exception message.
https://github.com/rubygems/rubygems/commit/bd3403da57
|
|
The `security_policies` method already requires it.
https://github.com/rubygems/rubygems/commit/d19b088f2f
|
|
It's checked before calling the method already.
https://github.com/rubygems/rubygems/commit/4eb00e9586
|
|
https://github.com/rubygems/rubygems/commit/a00c79a4da
|
|
Treats ::chmod_R and ::chown.
https://github.com/ruby/fileutils/commit/df4ac84bef
|
|
Treats ::chmod; adds Pathname usage to ::install.
https://github.com/ruby/fileutils/commit/9db4cb129c
|
|
`timeout 0.3.0` broke our test suite because we have some
tests that stubs `Process.clock_gettime` making it return
a value in the past, causing `Timeout` to trigger almost immediately.
I beleive it wasn't a problem before because it was relying on `Process.sleep`.
https://github.com/ruby/timeout/commit/e5911a303e
|
|
https://github.com/ruby/fileutils/commit/b9d5a79e38
|
|
Adds a note about file tree examples.
https://github.com/ruby/fileutils/commit/65ac65067a
|
|
https://github.com/rubygems/rubygems/commit/81ccb3ab89
|
|
#message (https://github.com/ruby/error_highlight/pull/24)
See https://bugs.ruby-lang.org/issues/18564.
Ref: https://github.com/ruby/did_you_mean/pull/177
https://github.com/ruby/error_highlight/commit/671b7c61b2
|
|
|
|
https://github.com/ruby/rdoc/commit/6d7bf24bb8
|
|
Currently only literal `0` and `1` are accepted as `read`/`write`
flags.
This patch allows other boolean arguments, C macros (`FALSE`/`TRUE`),
Ruby `VALUE`s (`Qfalse`/`Qtrue`), and C99 `bool`s (`false`/`true`), as
well.
https://github.com/ruby/rdoc/commit/169dc02e3c
|
|
(https://github.com/ruby/fileutils/pull/78)
Treats:
::rm
::rm_f
::rm_r
::rm_rf
::remove_entry_secure
https://github.com/ruby/fileutils/commit/ce2a438d75
|
|
* Add missing slash.
https://github.com/ruby/open-uri/commit/40023e63da
|
|
It was being explicitly required from `Gem::Specification` but also a
strange autoload was set for it at `Gem::Version`. The autoload was non
standard because it should've been done in the `Gem` module, not in
`Gem::Specification`, since that's where the constant is expected to get
defined. Doing this might get deprecated in the future, and it was not
being effective anyways due to the explicit require.
Unify everything with an `autoload` at the right place.
https://github.com/rubygems/rubygems/commit/174ea3e24c
|
|
https://github.com/ruby/cgi/commit/93326fb622
|
|
So that an exception raises by non-existent command, not via shell.
https://github.com/ruby/rdoc/commit/fd94dce69d
|
|
https://github.com/ruby/rdoc/commit/6b1a011243
|
|
https://github.com/ruby/rdoc/commit/83051403d6
|
|
`IO.popen` does that job.
https://github.com/ruby/rdoc/commit/3bbbc5ac84
|
|
https://github.com/ruby/rdoc/commit/47a1aef447
|
|
https://github.com/rubygems/rubygems/commit/a20bac7924
|
|
`Bundle.defintion`.
Prior to this commit, `bundle add GEM_NAME` updated the lockfile,
but `bundle remove GEM_NAME` left GEM_NAME in the lockfile.
By invalidating the cached `Bundle.definition`, the existing code
handles that without a problem.
https://github.com/rubygems/rubygems/commit/aa0794d6a9
|
|
The installer is actually rewriting the spec's full gem path to be the
one of the newly installed gem, however the accessor was not properly
working for `StubSpecification` instances, and default gems are always
of this type, because they are always present locally.
Fix the accessor to properly update the underlying full specification.
https://github.com/rubygems/rubygems/commit/efa41babfa
|