| Age | Commit message (Collapse) | Author |
|
If you start Ruby with `--yjit-disable`, the `+YJIT` shouldn't be
added until `RubyVM::YJIT.enable` is actually called. Otherwise
it's confusing in crash reports etc.
|
|
https://github.com/ruby/prism/commit/11e0e204ce
|
|
https://github.com/ruby/prism/commit/499ec1c3f1
|
|
https://github.com/ruby/prism/commit/27e7685dd4
|
|
https://github.com/ruby/prism/commit/953601e3c0
|
|
https://github.com/ruby/prism/commit/2e02fa3b80
|
|
https://github.com/ruby/prism/commit/e0e8bba8be
|
|
(https://github.com/ruby/irb/pull/964)
* Add accidentally dropped disable_irb command back
* Sort command files require by name
https://github.com/ruby/irb/commit/1d627cebca
|
|
(https://github.com/ruby/reline/pull/712)
* Add key binding matching status :matching_matched
* Simplify read_2nd_character
* Add a comment of matching status and EOF
* Matching status to a constant
* Expand complicated ternary operators to case-when
https://github.com/ruby/reline/commit/64deec100b
|
|
maciter
This test was accidentally passing the value 2048 into the keytype
parameter of PKCS12_create, not the mac_iter parameter (because it had
one too many `nil`s in the call). This value is invalid, and will make
OpenSSL perform an out-of-bounds read which is caught when compiling
with ASAN.
This commit fixes the tests, and also adds some validation to
PKCS12.create to make sure any keytype passed is actually valid. Since
there only two valid keytype constants, and the whole feature is an
export-grade crypto era thing only ever supported by old MSIE, it seems
far more likely that code in the whild is using keytype similarly by
mistake rather than as intended. So this validation might catch that.
https://github.com/ruby/openssl/commit/47028686d2
|
|
https://github.com/ruby/prism/commit/09ba678066
|
|
https://github.com/ruby/prism/commit/85b4a5f804
|
|
https://github.com/ruby/prism/commit/461aa5e658
|
|
https://github.com/ruby/prism/commit/c49efdf824
|
|
https://github.com/ruby/prism/commit/12e079c97e
|
|
(https://github.com/ruby/reline/pull/716)
https://github.com/ruby/reline/commit/f9227b5c89
|
|
is not.""
This reverts commit 6e84ac2359c8fc8cb686ef4644b9cae26cd5ab9e.
Now that the rubygems spec change has been merged, let's try reverting
this and fixing it with tompng's new patch.
|
|
translation""
This reverts commit https://github.com/ruby/prism/commit/d8ae19d0334a.
https://github.com/ruby/prism/commit/df1eda2811
|
|
Co-authored-by: "Nobuyoshi Nakada" <nobu@ruby-lang.org>
|
|
This reverts commit ba01d15cf5db96933905d669c68f5cc0cd6910b8.
It seems to be failing test-bundler-parallel. Reverting it to normalize
the CI. We should revert this revert once we figure it out.
|
|
This reverts commit https://github.com/ruby/prism/commit/823e931ff230.
https://github.com/ruby/prism/commit/d8ae19d033
|
|
https://github.com/ruby/prism/commit/823e931ff2
|
|
https://github.com/ruby/prism/commit/aee84cf42c
|
|
https://github.com/ruby/prism/commit/a255653447
|
|
https://github.com/ruby/prism/commit/95e2484903
|
|
(https://github.com/ruby/reline/pull/659)
Reline::ANSI has a partial non-tty supporting code. It should be a general io.
Reline::Dumb should be only used in testing.
https://github.com/ruby/reline/commit/2d6828473d
|
|
to the end of the line when there is no search substr
(https://github.com/ruby/reline/pull/714)
* In ed_search_prev_history, make the cursor come to the end of the line when there is no search substr
* In ed_search_next_history, make the cursor come to the end of the line when there is no search substr
* Implemented ActionState to search with empty substr if the previous operation was search with empty string.
* Use a simple 2-element array to represent action_state
https://github.com/ruby/reline/commit/95ee80bd70
|
|
(https://github.com/ruby/reline/pull/709)
* Improve key binding match/matching check
* Rename key_actors to default_key_bindings
* Make key_stroke.expand always return a value
* Update add_default_key_binding to use a add_default_key_binding_by_keymap internally
Co-authored-by: Stan Lo <stan001212@gmail.com>
---------
https://github.com/ruby/reline/commit/353ec236e2
Co-authored-by: Stan Lo <stan001212@gmail.com>
|
|
[Feature #20205]
Now that chilled strings no longer appear as frozen, there is no
need to offer an API to check for chilled strings.
We however need to change `rb_check_frozen_internal` to no
longer be a macro, as it needs to check for chilled strings.
|
|
|
|
(https://github.com/ruby/reline/pull/666)
* Overhaul IO gate structure
1. Move IO related classes to `lib/reline/io/` directory.
2. Rename `GeneralIO` to `Dumb`.
3. Use IO classes as instances instead of classes.
* Update lib/reline/io/ansi.rb
Co-authored-by: tomoya ishida <tomoyapenguin@gmail.com>
---------
https://github.com/ruby/reline/commit/dc1518e1ac
Co-authored-by: tomoya ishida <tomoyapenguin@gmail.com>
|
|
The keyword argument `anonymous` is implemented for `Tempfile.create`
The default is `anonymous: false`.
The behavior is not changed as before.
The created temporary file is immediately removed if `anonymous: true` is specified.
So applications don't need to remove the file.
The actual storage of the file is reclaimed by the OS when the file is closed.
It uses `O_TMPFILE` for Linux 3.11 or later.
It creates an anonymous file from the beginning.
It uses FILE_SHARE_DELETE for Windows.
It makes it possible to remove the opened file.
[Feature #20497]
|
|
https://github.com/ruby/prism/commit/a4e164e22b
|
|
https://github.com/ruby/prism/commit/840185110f
|
|
in parser
https://github.com/ruby/prism/commit/beed43922c
|
|
https://github.com/ruby/prism/commit/f2a327449a
|
|
https://github.com/ruby/prism/commit/785de2c39d
|
|
|
|
Blocks and keywords are allowed in regular index.
Also update NEWS to make this more clear.
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
installed
https://github.com/rubygems/rubygems/commit/1b5644b666
|
|
It's consistent with the previous test and makes print debugging easier.
https://github.com/rubygems/rubygems/commit/d7f424df16
|
|
Make it not also install the gem in the default GEM_HOME.
https://github.com/rubygems/rubygems/commit/22de9a810a
|
|
https://github.com/rubygems/rubygems/commit/33328e54fd
|
|
didn't verify the test is working properly due to mistaken auto-merge… [Bug #20515]
bug: https://bugs.ruby-lang.org/issues/20515
follow-up: 22e4eeda6561693367fc7a00b92b90f46b09cabd
follow-up: https://github.com/ruby/ruby/pull/10875
|
|
https://github.com/ruby/prism/commit/32277722d4
|
|
https://github.com/ruby/prism/commit/6f886be0a4
|
|
Avoid reoccurence of [Bug #20515]
Requires https://github.com/ruby/ruby/pull/10876 since 18eaf0be905e3e251423b42d6f4e56b7cae1bc3b
bug: https://bugs.ruby-lang.org/issues/20515
|
|
[Feature #20205]
Followup: https://github.com/ruby/stringio/pull/94
They no longer need to be special cases. If StringIO end up
mutating a chilled string, a warning will be emitted.
https://github.com/ruby/stringio/commit/dc62d65449
|
|
user installed gems"
This reverts commit a3edc4abc574b04bcacfae2af188cce7d27bfcf1.
That commit caused test failure with Windows platform.
* https://github.com/ruby/ruby/actions/runs/9289018414/job/25561871390
* https://github.com/ruby/ruby/actions/runs/9289018425/job/25561873060
|
|
installed gems
https://github.com/rubygems/rubygems/commit/0eb6ed8f86
|