| Age | Commit message (Collapse) | Author |
|---|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12157
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12157
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12157
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12157
|
|
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
Bumps the rb-sys group with 1 update in the /test/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib directory: [rb-sys](https://github.com/oxidize-rb/rb-sys).
Bumps the rb-sys group with 1 update in the /test/rubygems/test_gem_ext_cargo_builder/rust_ruby_example directory: [rb-sys](https://github.com/oxidize-rb/rb-sys).
Updates `rb-sys` from 0.9.102 to 0.9.103
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.102...v0.9.103)
Updates `rb-sys` from 0.9.102 to 0.9.103
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.102...v0.9.103)
---
updated-dependencies:
- dependency-name: rb-sys
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: rb-sys
- dependency-name: rb-sys
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: rb-sys
...
Signed-off-by: dependabot[bot] <support@github.com>
https://github.com/rubygems/rubygems/commit/31b8a68dd5
|
|
Due to a typo in the spec, the issue was not caught initially. If
Bundler does not need to re-resolve, `bundle lock` is a noop so Bundler
does not add checksums.
To fix the issue, we do something similar to what `bundle install` does,
just without actually installation. First set the domain (local or
remote) according to whether a re-resolve is necessary, and then
materialize lazy specifications into real specifications, so that
checksums are actually fetched from each source.
https://github.com/rubygems/rubygems/commit/84b6f4ee96
|
|
I always found the `resolve_if_necessary` method pretty confusing
because by reading it, it suggests that resolution always happens, and
the point is whether that needs to be local or remote. This commit tries
to make that more clear.
https://github.com/rubygems/rubygems/commit/93d6861ee8
|
|
All we need is to setup remote or local sources appropriately.
https://github.com/rubygems/rubygems/commit/3ceff46a2a
|
|
(https://github.com/ruby/reline/pull/782)
https://github.com/ruby/reline/commit/cbf213291c
|
|
The man page is clear that every `va_start` call MUST be succeeded by
the corresponding `va_end` call.
So `rb_raise` can't call `rb_exc_raise` before `va_end`, otherwise
`va_end` is never called.
Co-Authored-By: Étienne Barrié <etienne.barrie@gmail.com>
|
|
* bundler/lib/bundler/templates/newgem/README.md.tt (Development): Use the
test_task value to get the correct test task name ("test", not "test-unit").
* bundler/spec/commands/newgem_spec.rb (README.md): Add tests for test task
names for each test frameworks.
https://github.com/rubygems/rubygems/commit/2a24708a63
|
|
verbose mode
https://github.com/rubygems/rubygems/commit/585a6a89d4
|
|
https://github.com/rubygems/rubygems/commit/09e0971ab8
|
|
That's indeed the ideal behavior but it's a mess to maintain because the
version of RubyGems shipped with each patchlevel of Ruby changes. We
could try looking at the `VERSION` constant in `
RbConfig::CONFIG["rubylibdir"` but for now I calling what's in there now
as good enough.
https://github.com/rubygems/rubygems/commit/40ccf2b093
|
|
We already do this check in `setup.rb` itself, which is run earlier.
https://github.com/rubygems/rubygems/commit/160cc3f1c5
|
|
https://github.com/rubygems/rubygems/commit/31fadaf2d2
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12149
|
|
So that it doesn't get included in the generated binaries for builds
that don't support loading shared GC modules
Co-Authored-By: Peter Zhu <peter@peterzhu.ca>
Notes:
Merged: https://github.com/ruby/ruby/pull/12149
|
|
Co-Authored-By: Peter Zhu <peter@peterzhu.ca>
Notes:
Merged: https://github.com/ruby/ruby/pull/12149
|
|
```
for (int i = 0; i < arg->family_size; i++) {
arg->getaddrinfo_entries[i] = allocate_fast_fallback_getaddrinfo_entry();
if (!(arg->getaddrinfo_entries[i])) rb_syserr_fail(errno, "calloc(3)");
```
If the allocation fails in the second interation, the memory allocated
in the first iteration would be leaked.
This change prevents the memory leak by allocating the memory in
advance.
(The struct name `fast_fallback_getaddrinfo_shared` might no longer be
good.)
Notes:
Merged: https://github.com/ruby/ruby/pull/12163
|
|
`make test-all RUBYOPT=-w` in the ruby/ruby repo printed the warning.
This change prevents the warning by specifying the content-type
explicitly.
A follow-up to https://github.com/rubygems/rubygems/commit/b70c1bb1503d
https://github.com/rubygems/rubygems/commit/d573af07f6
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12161
|
|
https://github.com/ruby/open-uri/commit/04067e54b9
|
|
(https://github.com/ruby/uri/pull/138)
https://github.com/ruby/uri/commit/c00726a20a
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12160
|
|
|
|
* Do not save the last_error if there are no sockets waiting to be connected
In this implementation, the results of both name resolution and connection attempts are awaited using select(2).
When it returned, the implementation attempted to check for connections even if there were no sockets currently attempting to connect, treating the absence of connected sockets as a connection failure.
With this fix, it will no longer check for connections when there are no sockets waiting to be connected.
Additionally, the following minor fixes have been made:
* Handle failure of getsockopt(2) and removed unnecessary continue in the loop
* Tweak: Use common API to check in_progress_fds
* Safely call TCPServer.new in test
* Set empty writefds when there is no socket waiting to be connected
* Enable fast_fallback option
Notes:
Merged-By: shioimm <shioi.mm@gmail.com>
|
|
|
|
|
|
bug
(https://github.com/ruby/reline/pull/763)
https://github.com/ruby/reline/commit/d3ba7216eb
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12159
|
|
```
compiling gc.c
In file included from gc.c:80:
/usr/include/sys/prctl.h:88:8: error: redefinition of 'struct prctl_mm_map'
88 | struct prctl_mm_map {
| ^~~~~~~~~~~~
In file included from gc.c:79:
/usr/include/linux/prctl.h:134:8: note: originally defined here
134 | struct prctl_mm_map {
| ^~~~~~~~~~~~
```
The first include is not needed and is what causes this issue.
Two other places in ruby exclusively use the sys import.
See https://github.com/seccomp/libseccomp/issues/19 for a similar problem.
Notes:
Merged: https://github.com/ruby/ruby/pull/12154
|
|
[Bug #20907]
Notes:
Merged-By: ioquatix <samuel@codeotaku.com>
|
|
`rb_thread_call_without_gvl2` is used to wait for the results of name resolution and connection attempts.
When there is only one address family to resolve, the necessary resources were not being passed to the UBF.
With this change, the handling of resources has been revised and organized to work consistently, whether there are two address families to resolve or only one.
Notes:
Merged-By: shioimm <shioi.mm@gmail.com>
|
|
even if a system call error happens after the name resolution failure in the child thread.
pipe and write(2) are used to notify the main thread of the name resolution results from the child thread.
After name resolution is completed in the child thread, if the call to write(2) fails, the main thread retrieves the resolved addresses.
However, when name resolution failed, the corresponding error was not being saved in `last_error`.
With this change, name resolution failures will now be saved in last_error even if the write(2) call in the child thread fails.
Notes:
Merged-By: shioimm <shioi.mm@gmail.com>
|
|
ASAN_OPTIONS="detect_leaks=1" RUBY_FREE_AT_EXIT=1 ./miniruby -e 'trace_var(:$x){}'
Notes:
Merged: https://github.com/ruby/ruby/pull/12146
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12148
|
|
Allow CRLs to be signed using Ed25519 private keys by passing a nil digest.
https://github.com/ruby/openssl/commit/b62375bcde
|
|
Allow requests to be signed using Ed25519 private keys by passing a nil digest.
This is similar to commit https://github.com/ruby/openssl/commit/b0fc10009120 when signing certs.
Calling PKey#public_key is deprecated and does not work for Ed25519. The same
can be accomplished by passing the private key.
https://github.com/ruby/openssl/commit/d96090320d
|
|
test_pkey wasn't checking for libressl as is done elsewhere.
Note the libressl version check is different when testing pkey, because
PKey#sign relies on EVP_PKey_sign, whereas signing an X509 cert/request/crl
relies on ASN1_item_sign.
https://github.com/ruby/openssl/commit/f1db5c88a2
|
|
https://github.com/rubygems/rubygems/commit/9e0018d9fe
|
|
Update the default `NTVER`, so that the declarations of APIs
introduced since Windows 8 will be enabled.
https://learn.microsoft.com/cpp/porting/modifying-winver-and-win32-winnt
|
|
This commit adds extconf.rb for both the default GC and and MMTk to build
the external GC. This allows common.mk to not need to contain any
implementation-specific build configuration.
https://github.com/ruby/mmtk/commit/db6a29b4a9
|
|
This commit implements the mark-sweep algorithm using MMTk and allows
customizing the plan using MMTK_PLAN.
https://github.com/ruby/mmtk/commit/6fea5e5ffc
Co-Authored-By: Matt Valentine-House <matt@eightbitraptor.com>
|
|
This commit only supports initializing MMTk with NoGC and object
allocation.
https://github.com/ruby/mmtk/commit/39aa10e537
Co-Authored-By: Kunshan Wang <wks1986@gmail.com>
|
|
|
|
|
|
... to check the return value of ioctl
http://ci.rvm.jp/results/trunk_asan@ruby-sp1/5423172
```
/tmp/ruby/src/trunk_asan/lib/reline/io/ansi.rb:192: [BUG] rb_sys_fail_str(<STDIN>) - errno == 0
```
Notes:
Merged: https://github.com/ruby/ruby/pull/12147
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12145
|
