| Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
present
https://github.com/rubygems/rubygems/commit/28f4842196
|
|
* Make the supported check more obvious.
|
|
* See https://github.com/ruby/spec/pull/891
|
|
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
Since these regexps are used at build/installation, they are not
vulnerabilities.
Notes:
Merged: https://github.com/ruby/ruby/pull/5056
|
|
|
|
Previously obj_free returned true when it could not free a slot because
of a finalizer, and false when it successfully frees a slot.
Notes:
Merged: https://github.com/ruby/ruby/pull/5055
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5054
|
|
In the case of read-only but refering an unshareable object.
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5053
|
|
The ArgumentError should raise in `isolate`.
Notes:
Merged: https://github.com/ruby/ruby/pull/5053
|
|
invalid gemspec test compatible with ruby-trunk.
https://github.com/rubygems/rubygems/commit/a77061d4e9
|
|
at raised HTTP exception.
- this exception differs across Ruby versions.
https://github.com/rubygems/rubygems/commit/38c6927a5f
|
|
- previously it was required already by net/http, but it is not anymore using ruby-trunk
- https://github.com/ruby/net-http/commit/996d18a43f34557cb0b2fcf41b93131d48a235f4
- https://github.com/ruby/ruby/commit/364044e0909692315bd6c2f0e1d968ede9c2beb8#diff-a1d29a94def02829fd4f9ba591199acf079e028f5a2002a77c363eb01212e112
https://github.com/rubygems/rubygems/commit/be1779655a
|
|
downloader_spec.
- latest ruby adds error_highlight gem introducing backtrace into exception message
https://github.com/rubygems/rubygems/commit/08c70f9dd0
|
|
- latest ruby is shipped with racc 1.6 making this spec failing
- this spec is related to platform locking, changing version should not do any harm
https://github.com/rubygems/rubygems/commit/3e18b626cb
|
|
So that it loads a consistent version of the library and `rubygems` is
never affected by gem activation conflicts related to `tsort`.
Getting CI green required updating one `bundler` spec, because `tsort`
is no longer loaded by `bundle clean` until after `BUNDLE_PATH` has been
changed, so to ensure it is found, it needs to be installed under
`BUNDLE_PATH` as well (which will be different from the global system
path on Bundler 3, meaning installing `tsort` to the global system path
is not enough there). This spec workaround can be removed once we also
vendor `tsort` inside `bundler`.
https://github.com/rubygems/rubygems/commit/d326880999
|
|
Co-authored-by: Frederik Dudzik <frederik.dudzik@shopify.com>
Co-authored-by: Jacques Chester <jacques.chester@shopify.com>
|
|
- error_highlight was introduced at https://github.com/ruby/ruby/commit/e94604966572bb43fc887856d54aa54b8e9f7719
orriginally as error_squiggle later renamed at https://github.com/ruby/ruby/commit/9438c99590f5476a81cee8b4cf2de25084a40b42
- ruby2_keywords was introduced as a placeholder gem only at https://github.com/ruby/ruby/commit/21d2463fbc5094aa2ad92a21c910dccdc928b920
https://github.com/rubygems/rubygems/commit/c9ebe7c7d2
|
|
https://github.com/rubygems/rubygems/commit/a81d4421b4
|