| Age | Commit message (Collapse) | Author |
|
The "revision" attribute is actually getting the revision from the
Gemfile.lock file. So I think "locked" is a better term here to avoid
confusion with the revision checked out in `vendor/cache`.
https://github.com/rubygems/rubygems/commit/ca5bdebe1f
|
|
`len` is always at least 1 here.
Notes:
Merged: https://github.com/ruby/ruby/pull/12215
|
|
This could be out of GVL
Notes:
Merged: https://github.com/ruby/ruby/pull/12188
|
|
Let there be rooms for each GC implementations how to handle multi
threaded situations. They can be totally reentrant, or can have
their own mutex, or can rely on rb_thread_call_with_gvl.
In any ways the allocator (has been, but now officially is)
expected to run properly without a GVL. This means there need be
a way for them to inform the interpreter about their allocation
failures, without relying on raising exceptions.
Let them do so by returning NULL.
Notes:
Merged: https://github.com/ruby/ruby/pull/12188
|
|
|
|
https://github.com/ruby/set/commit/1c3cded76a
|
|
`TCPSocket.new` with HEv2 uses three threads.
The last of these threads to exit closed pipes.
However, if pipes were open at the end of the main thread, they would leak.
This change avoids this by closing pipes at the end of the main thread.
Notes:
Merged-By: shioimm <shioi.mm@gmail.com>
|
|
with `Socket.tcp_fast_fallback=`
The functions that `Socket.tcp` had are now also available in `TCPSocket.new`.
Notes:
Merged-By: shioimm <shioi.mm@gmail.com>
|
|
If `slave` is negative, neither `dup2(slave,0)` or `close(slave)` should
be executed. I believe this check is completely useless.
Notes:
Merged: https://github.com/ruby/ruby/pull/12207
|
|
Here `nb` should never be NULL. If it were, the following
`nb->buffer_list` would be strange.
A follow-up to ddd8da4b6ba3dfcca21ca710e7cef2fa3b9632d7
Notes:
Merged: https://github.com/ruby/ruby/pull/12208
|
|
This still support ruby 2.6 which does not require C99.
https://github.com/ruby/date/commit/61d849758f
|
|
It was used intentionally.
https://github.com/ruby/date/commit/291b40f939
|
|
https://github.com/ruby/time/commit/c668704413
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12205
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12205
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12205
|
|
This reverts commit 743a31d639d4c96827b1b17f59c829c1ec31abc3,
"[ruby/date] [DOC] Make document coverage 100%". This file is only
for rdoc coverage in the date gem, and useless when the built-in Time
is documented.
Notes:
Merged: https://github.com/ruby/ruby/pull/12206
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12202
|
|
When loading a crafted marshal data of Random, a pointer to an illegal
address was created. I don't think there is any harm since the data is
normalized before access, but just to be safe, I add a check to make it
an error.
Notes:
Merged: https://github.com/ruby/ruby/pull/12200
|
|
|
|
.git-blame-ignore-revs will be updated after this commit is merged.
Notes:
Merged: https://github.com/ruby/ruby/pull/12184
|
|
https://github.com/rubygems/rubygems/commit/23d06195fa
|
|
|
|
(https://github.com/ruby/reline/pull/786)
https://github.com/ruby/reline/commit/d4f6741e7e
|
|
With https://github.com/ruby/ruby/pull/12156,
the memory of the `struct fast_fallback_getaddrinfo_shared`
is now allocated even if there is only one address family.
This change will always free it when `TCPSocket.new` finishes.
Notes:
Merged-By: shioimm <shioi.mm@gmail.com>
|
|
This is not important because of the path of `assert(false)`, but just
in case.
Coverity Scan found this issue.
https://github.com/ruby/prism/commit/7335c62f9d
|
|
(https://github.com/ruby/rdoc/pull/1212)
Currently, the gemspec's files are defined by hand, which is error-prone.
For example: https://github.com/ruby/rdoc/pull/1211
This commit uses `Dir.glob` where possible to reduce the risk of that
happening again.
- Additional files added with this approach:
```
# This should have been added by only captured by this commit
lib/rdoc/parser/prism_ruby.rb
# These are folders and can be included/ignored either way
lib/rdoc/generator/template/darkfish
lib/rdoc/generator/template/darkfish/css
lib/rdoc/generator/template/darkfish/fonts
lib/rdoc/generator/template/darkfish/images
lib/rdoc/generator/template/darkfish/js
lib/rdoc/generator/template/json_index
lib/rdoc/generator/template/json_index/js
```
- Files that are ignored after this change:
```
# They make no difference on documentation generation
# Probably can be removed
lib/rdoc/generator/template/darkfish/.document
lib/rdoc/generator/template/json_index/.document
```
https://github.com/ruby/rdoc/commit/ac2a151f10
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12198
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12198
|
|
follow up: https://github.com/ruby/ruby/pull/12196/files#r1861730753
Notes:
Merged: https://github.com/ruby/ruby/pull/12197
|
|
from backtraces.
Notes:
Merged: https://github.com/ruby/ruby/pull/12196
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12196
|
|
After any `LINK_ELEMENT` sequence is added, `LINK_ANCHOR` must not
loop.
Notes:
Merged: https://github.com/ruby/ruby/pull/12195
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12193
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12193
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12193
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12193
|
|
A follow-up to ef59175a68c448fe334125824b477a9e1d5629bc. That commit
uses `&body->local_table[...]` but `body->local_table` is already freed.
I think it is an undefined behavior to calculate a pointer that exceeds
the bound by more than 1.
This change moves the free of `body->local_table` after the calculation.
Coverity Scan found this issue.
Notes:
Merged: https://github.com/ruby/ruby/pull/12194
|
|
The same issue as https://github.com/ruby/prism/pull/3246
Coverity Scan found this issue.
Notes:
Merged: https://github.com/ruby/ruby/pull/12192
|
|
|
|
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Notes:
Merged: https://github.com/ruby/ruby/pull/12187
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12187
|
|
|
|
When mmap fails for any reason, the fd must be closed.
Coverity Scan found this issue.
https://github.com/ruby/prism/commit/c06e9c400f
|
|
fill_lines is passed -1 for offset, which causes it to read the -1 index
of traces. This is not valid memory as -1 is reading before the trace
global variable in rb_print_backtrace. This code comes from commit
99d1f5f88b9b6de3124e31019902f91e030d334f, where there used to be special
handling for the -1 index.
We can see this error in ASAN:
==71037==ERROR: AddressSanitizer: global-buffer-overflow on address 0x00010157abf8 at pc 0x00010116f3b8 bp 0x00016f92c3b0 sp 0x00016f92c3a8
READ of size 8 at 0x00010157abf8 thread T0
#0 0x10116f3b4 in debug_info_read addr2line.c:1945
#1 0x10116cc90 in fill_lines addr2line.c:2497
#2 0x101169dbc in rb_dump_backtrace_with_lines addr2line.c:2635
#3 0x100e56788 in rb_print_backtrace vm_dump.c:825
#4 0x100e56db4 in rb_vm_bugreport vm_dump.c:1155
#5 0x100734dc4 in rb_bug_without_die error.c:1085
#6 0x100734ae4 in rb_bug error.c:109
Notes:
Merged: https://github.com/ruby/ruby/pull/12185
|
|
(https://github.com/ruby/reline/pull/785)
https://github.com/ruby/reline/commit/85e20f0031
|
|
(https://github.com/ruby/reline/pull/784)
https://github.com/ruby/reline/commit/a6d1ac54e6
|
|
macOS clang 16 generates DWARF5, which have Mach-O section names that
are limited to 16 characters, which causes sections with long names to
be truncated and not match above.
See: https://wiki.dwarfstd.org/Best_Practices.md#Mach-2d-O
Notes:
Merged: https://github.com/ruby/ruby/pull/12182
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12178
|
|
It's not used outside of error.c.
Notes:
Merged: https://github.com/ruby/ruby/pull/12183
|