Age | Commit message (Collapse) | Author |
|
It makes testing for JSON errors very tedious. You either have
to use a Regexp or to regularly update all your assertions
when JSON is upgraded.
https://github.com/flori/json/commit/de9eb1d28e
Notes:
Merged: https://github.com/ruby/ruby/pull/6200
|
|
https://github.com/ruby/date/commit/0cdbaa92e9
|
|
Should not be `Pathname::FileUtils`.
https://github.com/ruby/pathname/commit/d1eb366e73
|
|
|
|
|
|
rb_ary_tmp_new suggests that the array is temporary in some way, but
that's not true, it just creates an array that's hidden and not on the
transient heap. This commit renames it to rb_ary_hidden_new.
Notes:
Merged: https://github.com/ruby/ruby/pull/6180
|
|
The `rb_profile_frames` API did not skip the two dummy frames that
each thread has at its beginning. This was unlike `backtrace_each` and
`rb_ec_parcial_backtrace_object`, which do skip them.
This does not seem to be a problem for non-main thread frames,
because both `VM_FRAME_RUBYFRAME_P(cfp)` and
`rb_vm_frame_method_entry(cfp)` are NULL for them.
BUT, on the main thread `VM_FRAME_RUBYFRAME_P(cfp)` was true
and thus the dummy thread was still included in the output of
`rb_profile_frames`.
I've now made `rb_profile_frames` skip this extra frame (like
`backtrace_each` and friends), as well as add a test that asserts
the size and contents of `rb_profile_frames`.
Fixes [Bug #18907] (<https://bugs.ruby-lang.org/issues/18907>)
Notes:
Merged: https://github.com/ruby/ruby/pull/6114
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6174
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6166
|
|
Non-ASCII code may be negative on platforms plain char is signed.
Notes:
Merged: https://github.com/ruby/ruby/pull/6166
|
|
This reverts commit 79406e3600862bbb6dcdd7c5ef8de1978e6f916c.
Notes:
Merged: https://github.com/ruby/ruby/pull/6165
|
|
Sidekiq has a method named `❨╯°□°❩╯︵┻━┻`which corrupts
heap dumps.
Normally we could just dump is as is since it's valid UTF-8 and need
no escaping. But our code to escape control characters isn't UTF-8
aware so it's more complicated than it seems.
Ultimately since the overwhelming majority of method names are
pure ASCII, it's not a big loss to just skip it.
Notes:
Merged: https://github.com/ruby/ruby/pull/6161
|
|
[Misc #18891]
Notes:
Merged: https://github.com/ruby/ruby/pull/6094
|
|
|
|
|
|
When configuring with `--disable-rpath` and `--static-linked-ext` (e.g.
building for WASI), `extmk.rb` doesn't build exts under bundled gems,
and `.bundle/gems/#{gemname}-#{ver}` are not created due to no call of
`extmake`.
b2491783986084770f6f97552f27b868622730cf starts creating symlink at
`.bundle/gems/#{gemname}-#{ver}/lib`, but the parent dir is not created,
so configuration aginst debug and rbs gems were failed.
Notes:
Merged: https://github.com/ruby/ruby/pull/6136
|
|
https://github.com/ruby/psych/commit/6c56700fb2
|
|
These are used to see only if `RRATIONAL` and `RCOMPLEX` are
available, however, these two are macros and can be checked with
`#ifdef` directly.
https://github.com/ruby/bigdecimal/commit/175bbacd43
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6130
|
|
The default gems have not been installed yet in the build directory,
bundled gems depending on them can not work. As those dependencies
should be usable there even without rubygems, make temporary gemspec
files without the dependencies, and use them in the build directory.
Notes:
Merged: https://github.com/ruby/ruby/pull/6130
|
|
|
|
Treats:
#next
#<<
#>>
#next_month
#prev_month
#next_year
#prev_year
#step
#upto
#downto
https://github.com/ruby/date/commit/4246441a35
|
|
Minor edits to 11 methods' documentation.
https://github.com/ruby/date/commit/00bb7f6648
|
|
Omit private aliases from Rdoc.
https://github.com/ruby/date/commit/48f9180663
|
|
Minor changes (mostly doc-guide compliance) to 18 or so of simpler methods (getters).
https://github.com/ruby/date/commit/00e37ba2b4
|
|
The + tag can only be used for single words. For multiple words the <tt>
tag has to be used.
https://github.com/ruby/openssl/commit/cf2f019c3e
|
|
Openssl::OCSP::BasicResponse#sign is nil.
https://github.com/ruby/openssl/commit/27efcd7e1c
|
|
Openssl::OCSP::Request#sign is nil.
https://github.com/ruby/openssl/commit/a1f6cbc261
|
|
OSSL_LIBRESSL_PREREQ
https://github.com/ruby/openssl/commit/b02815271f
|
|
https://github.com/ruby/openssl/commit/e25fb0d0d8
|
|
suites along with some unit tests (https://github.com/ruby/openssl/pull/493)
Add OpenSSL::SSL::SSLContext#ciphersuites= method along with unit tests.
https://github.com/ruby/openssl/commit/12250c7cef
|
|
https://github.com/ruby/openssl/commit/b23fa75aa3
|
|
|
|
Brings a dozen call-seq schemas into compliance with the doc guide.
Adds links to section "Argument start" where needed.
Revises (minorly) ::today.
Otherwise, does not disturb existing text.
https://github.com/ruby/date/commit/9aec11df50
|
|
On Windows with OpenSSL 3, the gem fails to compile with the following
error message:
ruby/src/ext/openssl/extconf.rb:188: undefined method \`sub!' for nil:NilClass
This is because $warnflags is nil.
Notes:
Merged: https://github.com/ruby/ruby/pull/6102
|
|
[Bug #18900]
Thread#join and a few other codepaths are using native sleep as
a way to suspend the current thread. So we should call the relevant
hook when this happen, otherwise some thread may transition
directly from `RESUMED` to `READY`.
Notes:
Merged: https://github.com/ruby/ruby/pull/6101
|
|
All things commercial.
https://github.com/ruby/date/commit/9d3bc61728
|
|
|
|
https://github.com/ruby/date/commit/8eb1c780fb
Co-authored-by: Peter Zhu <peter@peterzhu.ca>
|
|
https://github.com/ruby/date/commit/e36690f70e
|
|
https://github.com/ruby/date/commit/dcc0742623
|
|
https://github.com/ruby/date/commit/91c632f156
|
|
https://github.com/ruby/date/commit/5c18ec031e
|
|
https://github.com/ruby/date/commit/fd3ae275c3
|
|
https://github.com/ruby/date/commit/ac25182c66
|
|
https://github.com/ruby/date/commit/f9ecaad2ee
|
|
https://github.com/ruby/date/commit/e80fee4f30
|
|
I suspect that some shared pages are invalidated because
some static string don't have their coderange set eagerly.
So the first time they are scanned, the entire memory page is
invalidated.
Being able to see the coderange in `ObjectSpace` would help debug
this.
And in addition `dump` currently call `is_broken_string()` and `is_ascii_string()`
which both end up scanning the string and assigning coderange. I think it's
undesirable as `dump` should be read only.
Notes:
Merged: https://github.com/ruby/ruby/pull/6076
|
|
https://github.com/ruby/bigdecimal/commit/3ede8860a6
|