| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/etc/commit/a8801e07d1
|
|
https://github.com/ruby/etc/commit/ea51739974
|
|
System-dependent feature macros are automatically detected by
extconf.rb, and are not used by users.
https://github.com/ruby/etc/commit/e7343b4e69
|
|
This is a verbose mode only warning.
Notes:
Merged: https://github.com/ruby/ruby/pull/6038
|
|
|
|
It often shows false positive warnings (at least in 4.8). Newer
versions work well and we can check correct warnings.
|
|
|
|
This script runs with BASERUBY, which can be as old as 2.2.x.
Exception#full_message is new in 2.5.0.
I saw a NoMethodError on the AppVeyor CI where BASERUBY is 2.4.6:
https://ci.appveyor.com/project/ruby/ruby/builds/43870654/job/kae4uo2xbhuhqmdw#L121
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6035
|
|
|
|
The GC compaction mechanism implements a kind of read barrier by marking
some (OS) pages as unreadable, and installing a SIGBUS/SIGSEGV handler
to detect when they're accessed and invalidate an attempt to move the
object.
Unfortunately, when a debugger is attached to the Ruby interpreter on
Mac OS, the debugger will trap the EXC_BAD_ACCES mach exception before
the runtime can transform that into a SIGBUS signal and dispatch it.
Thus, execution gets stuck; any attempt to continue from the debugger
re-executes the line that caused the exception and no forward progress
can be made.
This makes it impossible to debug either the Ruby interpreter or a C
extension whilst compaction is in use.
To fix this, we disable the EXC_BAD_ACCESS handler when installing the
SIGBUS/SIGSEGV handlers, and re-enable them once the compaction is done.
The debugger will still trap on the attempt to read the bad page, but it
will be trapping the SIGBUS signal, rather than the EXC_BAD_ACCESS mach
exception. It's possible to continue from this in the debugger, which
invokes the signal handler and allows forward progress to be made.
Notes:
Merged: https://github.com/ruby/ruby/pull/5991
|
|
Repeating to intern the same string is just redundant, as interned
strings for the same content are always the same object until it gets
collected.
Notes:
Merged: https://github.com/ruby/ruby/pull/6034
Merged-By: nobu <nobu@ruby-lang.org>
|
|
iseq_alloc is not used in compile.c. It is also a static function
declared in iseq.c so it's not accessible in compile.c.
|
|
(https://github.com/ruby/fileutils/pull/90)
* Revisions for module-level doc
https://github.com/ruby/fileutils/commit/dcbad90a1f
|
|
This commit makes `rp` report the correct array length in lldb.
When USING_RVARGC is set we use 7 bits of the flags to store the array
len rather than the usual 2, so they need to be part of the mask when
calculating the length in lldb.
When calculating whether rvargc is enabled I've used the same approach
that's used by `GC.using_rvargc?` which is to detect whether there is
more than one size pool in the current objspace.
Notes:
Merged: https://github.com/ruby/ruby/pull/6033
|
|
It previously failed with:
```
1) Failure:
TestThreadInstrumentation#test_thread_instrumentation_fork_safe [/home/runner/work/ruby/ruby/src/test/-ext-/thread/test_instrumentation_api.rb:50]:
<5> expected but was
<4>.
```
Suggesting one `EXIT` event wasn't fired or processed.
Adding an assetion on `Thead#status` may help figure out what is wrong.
Notes:
Merged: https://github.com/ruby/ruby/pull/6032
|
|
So that it does not interfere with our specs.
https://github.com/rubygems/rubygems/commit/1029714e21
|
|
https://github.com/rubygems/rubygems/commit/e07dba0923
|
|
https://github.com/rubygems/rubygems/commit/272ac23aa8
|
|
Instead, pass sitearchdir and sitelibdir directly to `make`.
This also removes the need to create and use the siteconf file at all
when generating makefiles.
https://github.com/rubygems/rubygems/commit/dea41fa2dc
|
|
This variable can't be falsy.
https://github.com/rubygems/rubygems/commit/b838f9a6f0
|
|
Only `RbConfig::MAKEFILE_CONFIG` is actually used.
https://github.com/rubygems/rubygems/commit/b767cc0929
|
|
[Feature #18339]
After experimenting with the initial version of the API I figured there is a need
for an exit event to cleanup instrumentation data. e.g. if you record data in a
{thread_id -> data} table, you need to free associated data when a thread goes away.
Notes:
Merged: https://github.com/ruby/ruby/pull/6029
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5867
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6017
|
|
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
Notes:
Merged: https://github.com/ruby/ruby/pull/6025
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6025
|
|
|
|
Follow up for 278fefb96294adf9d27a78f919c714a31b65ef58
|
|
Previously protected methods on refinements could never be called
because they were seen as being "defined" on the hidden refinement
ICLASS.
This commit updates calling refined protected methods so that they are
considered to be defined on the original class (the one being refined).
This ended up using the same behaviour that was used to check whether a
call to super was allowed, so I extracted that into a method.
[Bug #18806]
Notes:
Merged: https://github.com/ruby/ruby/pull/5966
|
|
Do not override the input string encoding at the time of preparation,
the source encoding is not determined from the input yet.
Notes:
Merged: https://github.com/ruby/ruby/pull/6015
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5207
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6021
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6021
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6030
|
|
https://github.com/ruby/fileutils/commit/13ab96439b
|
|
units
* Returning nil from the `content_range` method instead of raising an
error when the unit in the content-range header is not "bytes".
Fix https://bugs.ruby-lang.org/issues/11450
https://github.com/ruby/net-http/commit/0b5030dd86
Co-Authored-By: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
Commit 0c36ba53192c5a0d245c9b626e4346a32d7d144e changed GC compaction
methods to not be implemented when not supported. However, that commit
only does compile time checks (which currently only checks for WASM),
but there are additional compaction support checks during run time.
This commit changes it so that GC compaction methods aren't defined
during run time if the platform does not support GC compaction.
[Bug #18829]
Notes:
Merged: https://github.com/ruby/ruby/pull/6019
|
|
Naming this macro GC_COMPACTION_SUPPORTED is misleading because it
only checks whether compaction is supported at compile time.
[Bug #18829]
Notes:
Merged: https://github.com/ruby/ruby/pull/6019
|
|
This reverts commit 63546bfc1581d4abec2a0d846106a1c0afc0efa9.
|
|
Probably intended to pass encoding "none".
https://github.com/ruby/racc/commit/65cd26efd8
|
|
This function was added to a public header in [1] probably
unintentionally since it's not used anywhere, exposes implementation
details, and isn't related to the goals of that pull request.
[1]: 56cc3e99b6b9ec004255280337f6b8353f5e5b06
Notes:
Merged: https://github.com/ruby/ruby/pull/6023
Merged-By: XrXr
|
|
* Added a nil check in Net::HTTPHeader#initialize_http_header for keys in the header that do not have any value
* Returning nil from the content_range method instead of raising an error when the unit in the content-range header is not bytes
* Modified initialize_http_header to match trunk
fix [Bug #11450]
fix https://github.com/ruby/ruby/pull/1018
Notes:
Merged-By: nurse <naruse@airemix.jp>
|
|
|
|
|
|
|
|
|