| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
Check for TLS usability
On all platforms using GCC, even other than darwin.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Merge URI-0.10.2
* Merge URI-0.10.0.2 for bundler
* Added assert_linear_performance for URI tests
|
| |
|
| |
|
|
|
|
| |
until we figure out why it's failing.
|
| |
|
|
|
|
| |
https://github.com/ruby/ruby/actions/runs/4061314416/jobs/7033111867
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/ruby/actions/runs/3560006749/jobs/5979749144
|
|
|
|
|
| |
A bit readable to me.
See also https://github.com/ruby/ruby/pull/4880
|
|
|
|
|
|
|
|
|
| |
We've disabled MJIT CI on GitHub Actions for a while. It's convenient
that fork repositories need to see failures or disable it.
We should remove unused CI by default instead of silently disabling it.
Since I saw --mjit-wait passed on my fork, I'd like to try running
--mjit-wait one.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Rename --jit to --mjit
[Feature #18349]
* Fix a few more --jit references
* Fix MJIT Actions
* More s/jit/mjit/ and re-introduce --disable-jit
* Update NEWS.md
* Fix test_bug_reporter_add
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
[Bug #19187] Fix for tzdata-2022g
---
test/ruby/test_time_tz.rb | 21 +++++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)
|
| |
|
|
|
|
|
|
| |
The changes can be found at:
https://github.com/ruby/openssl/compare/v2.2.1...v2.2.2
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Followed up CVE-2022-39253 for bundler examples
---
spec/bundler/cache/git_spec.rb | 3 +++
spec/bundler/install/gemfile/git_spec.rb | 9 +++++++++
spec/bundler/update/git_spec.rb | 3 +++
3 files changed, 15 insertions(+)
|
|
|
|
|
|
|
|
|
| |
Use valid tokens as cookie names
---
spec/ruby/library/cgi/cookie/name_spec.rb | 12 ++++++------
spec/ruby/library/cgi/cookie/parse_spec.rb | 10 +++++-----
2 files changed, 11 insertions(+), 11 deletions(-)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dae843f6b7502f921a7e66f39e3714a39d860181,86096a91d55f72620e0f8ca8634da5fa342dc35b:
Bypass git submodule add/update with git config
protocol.file.allow=always option.
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
---
test/rubygems/test_gem_source_git.rb | 5 +++++
1 file changed, 5 insertions(+)
[rubygems/rubygems] Use [] instead of double-quotes
---
test/rubygems/test_gem_source_git.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
They removed https://zlib.net/zlib1212.zip because
https://zlib.net/zlib1213.zip was released :thinking_face:
Fix CI failures like:
https://ci.appveyor.com/project/ruby/ruby/builds/45064876/job/bb9biogolh0u2595
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since macOS 13, CFString family API used in
`rb_str_append_normalized_ospath` may internally use Objective-C classes
(`NSTaggedPointerString` and `NSPlaceholderMutableString`) for small strings.
On the other hand, Objective-C classes should not be used for the first
time in a `fork()`'ed but not `exec()`'ed process. Violations for this rule
can result deadlock during class initialization, so Objective-C runtime
conservatively crashes on such cases by default.
Therefore, we need to use CFString API to initialize Objective-C classes
used internally *before* `fork()`.
For more details, see https://bugs.ruby-lang.org/issues/18912
|
|
|
|
|
|
|
| |
The warning against `-undefined dynamic_lookup` is just a warning yet,
and many gems seem to pay no attention to warnings. Until it fails
actually, keep it as a migration path, except for standard extension
libraries and bundled extension gems.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Co-authored-by: Yuta Saito <kateinoigakukun@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Treat NULL fake string as an empty string
And the NULL string must be of size 0.
---
string.c | 5 +++++
1 file changed, 5 insertions(+)
|
|
|
|
|
|
|
|
| |
Return `false` where sticky-bit is not provided [Bug #18734]
---
file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
| |
[Win32] Fix mode of character/pipe device stat [Bug #18732]
|
| |
|
| |
|
| |
|
|
|
|
|
| |
And not depend on the state of rack's master branch, in particular, on
their Ruby support range.
|
|
|
|
|
|
|
| |
`RSpec::Mocks::ArgumentListMatcher#args_match?` fails when a
non-keywords hash is passed while a keyword hash is expected.
This is a change in `rspec-mocks` 3.10.3, so we need to adapt to it.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Update zlib version to 1.2.12
---
.appveyor.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
|