| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
present
https://github.com/rubygems/rubygems/commit/28f4842196
|
|
|
|
| |
* Make the supported check more obvious.
|
|
|
|
| |
* See https://github.com/ruby/spec/pull/891
|
| |
|
|
|
|
|
| |
Since these regexps are used at build/installation, they are not
vulnerabilities.
|
| |
|
|
|
|
|
| |
Previously obj_free returned true when it could not free a slot because
of a finalizer, and false when it successfully frees a slot.
|
| |
|
|
|
|
| |
In the case of read-only but refering an unshareable object.
|
| |
|
|
|
|
| |
The ArgumentError should raise in `isolate`.
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
We have a quality spec that check for debugger statements. Rubocop has a
cop that tests for the same thing. As such it makes sense to remove the
spec and activate the cop.
https://github.com/rubygems/rubygems/commit/dc1eb6eec5
|
| |
|
| |
|
|
|
|
| |
This caused Bus error on 32 bit Solaris
|
|
|
|
|
|
|
|
| |
On GitHub Actions, the macOS runners seem much more expensive than
Ubuntu, and its limit is the most significant bottlenecks for our
CIs. As the "check" tasks usually finish 3 or 4 times faster than
"test-bundler-parallel", it will be balanced by running all three
"check" tasks sequentially.
|
|
|
|
|
| |
* The worker timeouts seem working for test-all.
* The bundled gems have increased.
|
|
|
| |
Mostly adding blank line before and after code segment, to improve compliance with doc\documentation_guide.rdoc.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Treats:
#eql?
#<+>
#floor
#ceil
#round
#truncate
#step
|
|
|
|
|
| |
Since the YJIT Ruby module is CRuby specific and not meant for general
use, it should live under RubyVM instead of at top level.
|
|
|
|
|
|
|
|
| |
Rescuing all errors here might end up hiding other errors if the
deletion of the cached gem itself raises an error for some reason. Let's
be more conservative.
https://github.com/rubygems/rubygems/commit/3d80dfba08
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
zlib.net rarely returns the current time in RFC 2616 noncompliant
format in the response header, and the checksum does not match in
that case (maybe creating the tarball on the fly?).
|
|
|
|
|
| |
`struct vtm::year` is a Ruby integer instance, but not a C integer
type.
|
|
|
|
| |
it's start irb on built ruby (not installed ruby).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
```
../gc.c:2342:45: warning: comparison of integers of different signs: 'short' and 'size_t' (aka 'unsigned long') [-Wsign-compare]
GC_ASSERT(size_pools[pool_id].slot_size == slot_size);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
```
Add cast to short, because `GC_ASSERT`s in `size_pool_for_size`
already use cast to short.
|
|
|
|
|
|
|
|
| |
```
../gc.c:2342:25: warning: array subscript is of type 'char' [-Wchar-subscripts]
GC_ASSERT(size_pools[pool_id].slot_size == slot_size);
^~~~~~~~
```
|
|
|
|
|
| |
Since 46b66eb9e8e6de2d5750591e532310e8f8599d90, already `ary` has
been enclosed in `embed`.
|
| |
|
|
|
|
|
|
| |
This change fixes `-v --yjit-stats`. Previously in this situation,
YJIT._print_stats wasn't defined as yjit.rb is not evaluated when there
is only "-v" and no Ruby code to run.
|
|
|
|
|
|
| |
On -DRUBY_DEVEL builds, `ruby -v` can print extra info about the last
commit on a separate line, breaking some tests that expect a single
line. Assert only the first line instead.
|