Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/f328ef6f77
|
|
https://github.com/ruby/net-http/commit/2a97b4729b
|
|
https://github.com/ruby/net-http/commit/dada6007bf
|
|
The last_communicated timestamp is for HTTP persistent connection, to
decide whether the current TCP connection may be reused for the
subsequent requests or not. Naturally, the timer must be reset if the
connection is recreated since it is no longer relevant.
https://github.com/ruby/net-http/commit/0a013de42d
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5076
|
|
https://github.com/ruby/racc/commit/1f52571225
|
|
https://github.com/ruby/racc/commit/03d0b86b90
|
|
|
|
https://github.com/ruby/rdoc/commit/8386333323
|
|
https://github.com/ruby/openssl/commit/708ebf2f7a
|
|
https://github.com/ruby/optparse/commit/0aa18752cf
|
|
|
|
https://github.com/rubygems/rubygems/commit/b3e985799e
|
|
... to absorb a change on Ubuntu 21.10
|
|
* Mention `\0`
* Make the example of hash replacement meaningful
|
|
|
|
Treated:
#slice!
#sub
#sub!
#gsub
#gsub!
Notes:
Merged-By: BurdetteLamar <BurdetteLamar@Yahoo.com>
|
|
The check had not work because "headers" were not passed.
|
|
|
|
|
|
This fixes the following test error testing against OpenSSL 3.x:
~~~
2) Failure:
TestGemRequest#test_verify_certificate_extra_message [/builddir/build/BUILD/ruby-3.0.2/test/rubygems/test_gem_request.rb:358]:
<"ERROR: SSL verification error at depth 0: invalid CA certificate (24)\n" +
"ERROR: Certificate is an invalid CA certificate\n"> expected but was
<"ERROR: SSL verification error at depth 0: invalid CA certificate (79)\n" +
"ERROR: Certificate is an invalid CA certificate\n">.
~~~
Where the root cause is this OpenSSL commit:
https://github.com/openssl/openssl/commit/1e41dadfa7b9f792ed0f4714a3d3d36f070cf30e
It seems that OpenSSL upstream considers the constant value just an
implementation detail and therefore this changes the test case to
follow the suite.
https://github.com/rubygems/rubygems/commit/8acf8e95dc
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5069
|
|
Readline seems to emit an escape sequence `"\e[?1034h` at an
unpredictable timing when `TERM=xterm` or something.
This leads to a noisy random test failure.
http://rubyci.s3.amazonaws.com/amazon2/ruby-master/log/20211102T063005Z.fail.html.gz
```
1) Failure:
TestReadline#test_modify_text_in_pre_input_hook [/home/chkbuild/chkbuild/tmp/build/20211102T063005Z/ruby/test/readline/test_readline.rb:404]:
<"> hello world\n"> expected but was
<"\e[?1034h> hello world\n">.
```
This test is for Ruby's readline extension, not for readline library
itself. So here this change force to use "TERM=vt100" to run the tests.
|
|
|
|
|
|
|
|
|
|
|
|
So that system man pages still work after a gem with man pages overrides
it.
https://github.com/rubygems/rubygems/commit/1031879b87
|
|
* YJIT: Support kwargs sends with all defaults
Previously keyword argument methods were only compiled by YJIT when all
keywords were specified in the caller.
This adds support for calling methods with keyword arguments when no
keyword arguments are specified and all are filled with the defaults.
* Remove unused send_iseq_kwargs_none_passed
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
Add docs for X509::Name.parse_openssl and X509::Name.parse_rfc2253,
which are currently undocumented despite being widely used.
Small changes are also made to #to_s and the class description to
recommend using RFC 2253-based methods.
Fixes: https://github.com/ruby/openssl/issues/470
https://github.com/ruby/openssl/commit/74041a35d4
|
|
OpenSSL::SSL::SSLSocket allowed #read and #write to be called before an
SSL/TLS handshake is completed. They passed unencrypted data to the
underlying socket.
This behavior is very odd to have in this library. A verbose mode
warning "SSL session is not started yet" was emitted whenever this
happened. It also didn't behave well with OpenSSL::Buffering. Let's
just get rid of it.
Fixes: https://github.com/ruby/openssl/issues/9
https://github.com/ruby/openssl/commit/bf780748b3
|
|
|
|
|
|
|
|
Calling `Bundler.definition.specs` will memoize materialized specs.
However, requiring `bundler/setup` will end up materializing the same
set of specs, but not memoize them.
This change makes things consistent.
https://github.com/rubygems/rubygems/commit/e4c2b52824
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5065
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5064
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5064
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5063
Merged-By: nobu <nobu@ruby-lang.org>
|
|
|
|
Signed-off-by: Ulysse Buonomo <buonomo.ulysse@gmail.com>
Notes:
Merged: https://github.com/ruby/ruby/pull/4894
|
|
This change adds --with-thread=IMPL option to the configure. If not
supplied, default implementation for each platform will be used.
Notes:
Merged: https://github.com/ruby/ruby/pull/5043
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5043
|
|
This is a first step to allow the thread-model implementation to be
switched by configure's option
Notes:
Merged: https://github.com/ruby/ruby/pull/5043
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4970
|
|
This may break linking on GitHub, but it's more important for the
links to work in the documentation generated by rdoc.
Fixes [Bug #14743]
Notes:
Merged: https://github.com/ruby/ruby/pull/4958
|
|
Magic comments like `frozen_string_literal` may appear everywhere
within the first comment section while `encoding` have to be the first
line, or second line after shebang.
Notes:
Merged: https://github.com/ruby/ruby/pull/4985
|