Age | Commit message (Collapse) | Author |
|
|
|
It seems that since ruby openssl 2.1.0 [[1]], the distinguished name
submitted to `OpenSSL::X509::Name.parse` is not correctly parsed if it
does not contain the first slash:
~~~
$ ruby -v
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux]
$ gem list | grep openssl
openssl (default: 2.2.0)
$ irb -r openssl
irb(main):001:0> OpenSSL::X509::Name.parse("CN=nobody/DC=example").to_s(OpenSSL::X509::Name::ONELINE)
=> "CN = nobody/DC=example"
irb(main):002:0> OpenSSL::X509::Name.parse("/CN=nobody/DC=example").to_s(OpenSSL::X509::Name::ONELINE)
=> "CN = nobody, DC = example"
~~~
Instead, use `OpenSSL::X509::Name.new` directly as suggested by upstream
maintainer.
[1]: https://github.com/ruby/openssl/commit/19c67cd10c57f3ab7b13966c36431ebc3fdd653b
https://github.com/rubygems/rubygems/commit/09ca0c2dae
Co-authored-by: Kazuki Yamaguchi <k@rhe.jp>
|
|
|
|
bundler/lib/bundler/templates/newgem/github/workflows/main.yml.tt
https://github.com/rubygems/rubygems/commit/8836fe157b
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
|
|
https://github.com/rubygems/rubygems/commit/3260173c59
|
|
https://github.com/rubygems/rubygems/commit/f5bead5634
|
|
This change avoids a YAML Float-to-String conversion, which turns a 3.0 into a "3". That can make names of builds less clear.
In order to use this new capability, I added a "name" descriptor to the matrix-created Job.
https://github.com/rubygems/rubygems/commit/6221241ad4
|
|
concurrently
When bundler parallel installer installs gems concurrently, one can get
confusing warnings like the following:
```
"[/home/runner/work/rubygems/rubygems/bundler/tmp/2/gems/system/specifications/zeitwerk-2.4.2.gemspec] isn't a Gem::Specification (NilClass instead).
```
I've got these warnings several times in the past, but I never managed
to reproduce them, and never look deeply into the root cause, but this
time a got a cause that reproduced quite frequently, so I looked into
it.
The problem is one thread reading a gemspec while another thread is
writing it. The write of the gemspec was not protected, so
`Gem::Specification.load` could end up seeing a truncated gemspec and
thus throw this warning.
The fix involve two changes:
* Change the methods that write gemspecs to use `Gem.binary_write` which
is protected by a lock.
* Fix `Gem.binary_write` to create the file lock at file creation time,
not when the file already exists after.
The realworld user problem caused by this issue happens in bundler, but
I'm fixing it in rubygems first, and then I'll backport to bundler
whatever needs backporting to fix the issue on the bundler side.
https://github.com/rubygems/rubygems/commit/a672e7555c
|
|
This reverts commit af604436d8141c34cb2e1e645b9b0d47bfd55a55.
The issue that led to introducing it was never reproduced. I tried to
repro with this patch and it still works just fine. Since this removal
is getting in the middle for some race conditions I'm facing, I'm
reverting the patch.
https://github.com/rubygems/rubygems/commit/2dd267f0e4
|
|
At least, Error::ENOTSUP may be raised on some extreme environments
https://github.com/ruby/error_highlight/commit/2787983ff7
|
|
According to nobu, Errno::EBAD is raised on Windows.
|
|
The error is raised on Solaris
http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20211130T030003Z.fail.html.gz
```
1) Failure:
TestRubyOptions#test_require [/export/home/users/chkbuild/cb-gcc/tmp/build/20211130T030003Z/ruby/test/ruby/test_rubyoptions.rb:265]:
pid 7386 exit 1
| /export/home/users/chkbuild/cb-gcc/tmp/build/20211130T030003Z/ruby/lib/pp.rb:67:in `winsize': Invalid argument - <STDOUT> (Errno::EINVAL)
```
|
|
[Feature #12913]
|
|
https://github.com/rubygems/rubygems/commit/3ede1435ea
|
|
https://github.com/rubygems/rubygems/commit/62d54cbf08
|
|
When already set by `use_lib_reline` in test/readline/helper.rb of
readline-ext.
https://github.com/ruby/readline/commit/0e3ca3b217
|
|
Backquotes are not special characters in RDoc.
https://github.com/ruby/ostruct/commit/a901df26b9
|
|
https://github.com/ruby/cgi/commit/e840b6c368
|
|
Fix https://github.com/ruby/cgi/pull/11
https://github.com/ruby/cgi/commit/60d8f5e7d9
|
|
https://github.com/rubygems/rubygems/commit/0396e899db
|
|
So that version dependent pkg-config files can override files in
the default locations.
Notes:
Merged: https://github.com/ruby/ruby/pull/5182
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5182
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5182
|
|
been deleted
https://github.com/rubygems/rubygems/commit/fe1a31db31
|
|
https://github.com/rubygems/rubygems/commit/8dc86b7096
|
|
https://github.com/ruby/cgi/commit/c9c800715e
|
|
https://github.com/ruby/cgi/commit/052eb3a828
|
|
https://github.com/rubygems/rubygems/commit/7f22fe56b3
|
|
fix https://github.com/ruby/irb/issues/308
This bug occurred when `dialog.width - calculate_width(s, true)` was negative.
When `dialog.width` is shorter than `old_dialog.width`, it calculates how much padding it has to do. However, there are cases where `s` is longer than `dialog.width`, as in the issue. In that case, `padding_space_with_escape_sequences` will crash.
Here, `old_dialog.width` is longer than `dialog.width`, so I changed the padding width to `old_dialog.width - dialog.width`.
https://github.com/ruby/reline/commit/c581c31e0f
|
|
Just duplications.
|
|
https://github.com/rubygems/rubygems/commit/3241b34055
|
|
Gemfile
https://github.com/rubygems/rubygems/commit/6a19cca7e5
|
|
https://github.com/rubygems/rubygems/commit/e896e63ac3
|
|
https://github.com/rubygems/rubygems/commit/afaf868b68
|
|
https://github.com/rubygems/rubygems/commit/c8cc053bde
|
|
https://github.com/rubygems/rubygems/commit/5cb0b9d9b8
|
|
https://github.com/rubygems/rubygems/commit/662de0c990
|
|
https://github.com/rubygems/rubygems/commit/19f117652b
|
|
https://github.com/rubygems/rubygems/commit/231be44d38
|
|
https://github.com/rubygems/rubygems/commit/54e923ffc2
|
|
To spare the `defined?` check.
https://github.com/rubygems/rubygems/commit/64d27bba01
|
|
This gem exposes no executable files.
https://github.com/ruby/net-http/commit/3b3743f6ce
|
|
https://github.com/ruby/ipaddr/commit/37007e7812
|
|
https://github.com/ruby/net-protocol/commit/d4982420e6
|
|
https://github.com/ruby/set/commit/db2ebc946d
|
|
Picked from https://github.com/rubygems/rubygems/commit/4b498709a015a94e14a3852a1841a7a3e669133d
|
|
https://github.com/ruby/net-http/commit/9d95c5e3e6
|
|
RDoc expects example code to be valid syntax.
https://github.com/ruby/tmpdir/commit/ee42540ebb
|
|
Previously, the command string to be used for the shell command
was first generated and then split using shellsplit. This change
reverts the current behavior as it breaks if the value of remote
contains a space.
https://github.com/rubygems/rubygems/commit/6649ee10b0
|
|
https://github.com/rubygems/rubygems/commit/a54cca13db
|