| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Also defined in include/ruby/internal/core/rarray.h which always
will be included.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
multithreaded use
I'm not sure whether this handles all multithreaded use cases,
but this handles the example that crashes almost immediately
and does 10,000,000 total deflates using 100 separate threads.
To prevent the tests from taking forever, the committed test
for this uses only 10,000 deflates across 10 separate threads,
which still causes a segfault in the previous implementation
almost immediately.
Fixes [Bug #17803]
https://github.com/ruby/zlib/commit/4b1023b3f2
|
|
|
|
|
|
|
| |
Improve the language in the gem's summary and description;
also remove U+00A0 (no-break space) characters from post-install box.
https://github.com/ruby/readline/commit/5037cf7ffc
|
|
|
|
|
|
| |
This gem exposes no executables.
https://github.com/ruby/resolv-replace/commit/fa405185f7
|
|
|
|
| |
https://github.com/ruby/resolv/commit/095f1c003f
|
|
|
|
|
|
| |
We would like to avoid linking to the Set class for these words.
https://github.com/ruby/getoptlong/commit/33b56d6141
|
|
|
|
|
|
| |
This gem exposes 0 executables.
https://github.com/ruby/getoptlong/commit/4522163cbd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When attempting to require a file without an extension that has
already been required or provided with an .so extension, only
look for files with an .rb extension. There is no point in
trying to find files with an .so extension, since we already
know one has been loaded.
Previously, attempting to require such a file scanned the load
path twice, once for .rb and once for .so. Now it only scans
once for .rb. The scan once for .rb cannot be avoided, since
the .rb file would take precedence and should be loaded if it
exists.
Fixes [Bug #10902]
|
|
|
|
| |
https://github.com/ruby/digest/commit/360a7de366
|
|
|
|
|
|
| |
Gem::Specification#add_development_dependency
https://github.com/ruby/digest/commit/460a6f807e
|
|
|
|
| |
https://github.com/ruby/digest/commit/23dc9c7425
|
|
|
|
| |
https://github.com/ruby/digest/commit/82fb618157
|
|
|
|
| |
https://github.com/ruby/digest/commit/0a451e0c94
|
|
|
|
| |
https://github.com/ruby/digest/commit/086d54ba94
|
|
|
|
|
|
| |
This makes it slightly more explicit that this is not a definite new version.
https://github.com/ruby/digest/commit/2bb5bb78a3
|
|
|
|
|
|
| |
This is a test, to see if the build failures are about the shipped Ruby master version of this gem.
https://github.com/ruby/digest/commit/d2606b2cce
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 13f8521c630a15c87398dee0763e95f59c032a94.
http://rubyci.s3.amazonaws.com/solaris11-gcc/ruby-master/log/20210727T230009Z.fail.html.gz
http://rubyci.s3.amazonaws.com/solaris11-sunc/ruby-master/log/20210728T000009Z.fail.html.gz
This revert is to confirm whether the commit is the cause.
If the failures consistently occur after this revert, I'll
reintroduce the commit.
|
|
|
|
|
|
|
| |
Document that only first 9 numbered capture groups can use the \n
backreference syntax. Document \0 backreference. Document \K anchor.
Fixes [Bug #14500]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous implementation could result in a returned
float that is 1/(10**ndigits) too low. First try adding
one before dividing, and if that results in a value that is
greater than the initial number, then try the original
calculation.
Spec added for ciel, but the issue doesn't appear to affect
ciel, at least not for the same number. If the issue does
effect ciel, a similar fix could probably work for it.
Fixes [Bug #18018]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
VM patch from wanabe.
Test based on example from buzztaiki (Taiki Sugawara).
Test fails when compiles with -DRUBY_DEBUG, as that can
can use rb_bug instead of NoMemoryError, which doesn't
allow testing this case. Test also fails on MingW, as
RangeError is used instead of NoMemoryError. Skip the
test in either case.
Fixes [Bug #15779]
|
|
|
|
|
|
|
|
|
| |
This error can occur on Windows for certain filenames on certain
code pages.
Fixes [Bug #14591]
https://github.com/ruby/find/commit/0a474d1027
|
| |
|
|
|
|
|
| |
Detect Unicode ranges and loop over them.
This fixes issue #18028.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Deal with the issue that the emoji files in emoji/13.1 have Unicode
Emoji version 13.1, but at the same time the files in 13.0.0/ucd/emoji
are still at Emoji version 13.0. Specifically:
- Add a version attribute to TestEmojiBreaks::BreakFile
- Take the version for emoji-variant-sequences.txt from the Unicode
version, removing the last two characters.
- Improve information in exceptions for file name and version mismatches.
|
| |
|
|
|
|
| |
https://github.com/ruby/uri/commit/bbf8b44dba
|
|
|
|
|
|
|
| |
* Using a module to map scheme name to scheme class, which also works with Ractor.
* No constant redefinition, no ObjectSpace, still fast lookup for initial schemes.
https://github.com/ruby/uri/commit/883567fd81
|
|
|
|
|
|
|
| |
* This reverts commit 1faa4fdc161d7aeebdb5de0c407b923beaecf898.
* It has too many problems, see https://github.com/ruby/uri/pull/22 for discussion.
https://github.com/ruby/uri/commit/b959da2dc9
|
|
|
|
| |
https://github.com/ruby/uri/commit/1faa4fdc16
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
If the thread termination invokes user code after `th->status` becomes
`THREAD_KILLED`, and the user unblock function causes that `th->status` to
become something else (e.g. `THREAD_RUNNING`), threads waiting in
`thread_join_sleep` will hang forever. We move the unblock function call
to before the thread status is updated, and allow threads to join as soon
as `th->value` becomes defined.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Consume the VM stack more, to make the target object get GCed with
more probability during suppressing the warning.
|
| |
|
|
|
|
|
|
|
|
| |
Bundler has deprecated gemfiles without a global source and this feature
is now obsolete. `Bundler::Definition#has_rubygems_remotes?` is removed
because it's not used anymore.
https://github.com/rubygems/rubygems/commit/d29dd2cb7b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
improve readability
`check_rubygems_source_safety` is responsible for:
1. if there are multiple global sources
- for bundle 3.x raise an error
- for bundle 2.x print a warning
2. print a warning if there is no explicit global source
The second responsibility was added recently and now the logic could be
extracted to improve readability. Conditions are still live in the `check_rubygems_source_safety` method
since we don't want to call both functions always and that would help us achieve that.
https://github.com/rubygems/rubygems/commit/f3d7e946ee
|
|
|
|
|
|
| |
Raise a warning when parsing a Gemfile and it doesn't have a global source. Gemfiles like this, specially now that rubygems sources are are no longer merged into a single source for security, are very confusing because they generate a different lockfile depending on the gems you have locally installed. This is because bundler always use an implicit global source that defaults to locally installed gems.
https://github.com/rubygems/rubygems/commit/b7523ad21c
|
|
|
|
|
|
| |
This is in preparation for deprecating source-less gemfiles.
https://github.com/rubygems/rubygems/commit/d6493fa3e2
|
|
|
|
|
|
| |
This method is created to tell whether any global source exist in the object or not and it will be used by `Bundler:Dsl` to print a warning if no global source has been defined in the Gemfile.
https://github.com/rubygems/rubygems/commit/422fec4438
|