ruby.git/test/irb/test_history.rb, branch v3_3_11

[Bug #20511] Update reline-0.5.7 (#10848)

2024-05-28T22:54:39+00:00

* Update reline-0.5.7

* Update irb-1.13.1

Save $VERBOSE properly

2023-12-12T02:06:27+00:00

Prevent a warning: setting Encoding.default_external

2023-12-12T01:31:37+00:00

[ruby/irb] Scrub past history input before split

2023-12-01T18:04:03+00:00

(https://github.com/ruby/irb/pull/795)

* Scrub past history input before split

* Don't rewrite ENV["LANG"]

https://github.com/ruby/irb/commit/0f344f66d9

[ruby/irb] Handle Concurrent Sessions and Saving Readline::HISTORY

2023-09-16T12:48:32+00:00

(https://github.com/ruby/irb/pull/651)

* handle concurrent sessions and saving Readline::HISTORY, fixes https://github.com/ruby/irb/pull/510

* separate tests

* don't mutate the HISTORY object on the class

* avoid repeated .to_i calls

* remove intermediary history array

* work with array, fix test comment

---------

https://github.com/ruby/irb/commit/1681ada328

Co-authored-by: Stan Lo

[ruby/irb] Avoid overriding user's `irb_name` setting in debugger

2023-08-21T18:23:32+00:00

integration
(https://github.com/ruby/irb/pull/688)

* Avoid overriding user's irb_name setting in debugger integration

Instead of always setting `irb_name` to `irb:rdbg`, it should respect
the user's setting and only append `:rdbg` to it.

* Introduce write_rc test helper

https://github.com/ruby/irb/commit/2ce7593351

[ruby/irb] Support seamless integration with ruby/debug

2023-08-13T18:30:34+00:00

(https://github.com/ruby/irb/pull/575)

* Support native integration with ruby/debug

* Prevent using multi-irb and activating debugger at the same time

Multi-irb makes a few assumptions:

- IRB will manage all threads that host sub-irb sessions
- All IRB sessions will be run on the threads created by IRB itself

However, when using the debugger these assumptions are broken:

- `debug` will freeze ALL threads when it suspends the session (e.g. when
  hitting a breakpoint, or performing step-debugging).
- Since the irb-debug integration runs IRB as the debugger's interface,
  it will be run on the debugger's thread, which is not managed by IRB.

So we should prevent the 2 features from being used at the same time.
To do that, we check if the other feature is already activated when
executing the commands that would activate the other feature.

https://github.com/ruby/irb/commit/d8fb3246be

[ruby/irb] Skip integration tests in core CI

2023-08-11T18:27:17+00:00

(https://github.com/ruby/irb/pull/677)

We already skipped history integration tests in core CI in #675 due to
suspicion on nested IRB sessions don't work on certain operating systems.

But after #669, the evaluation integration test also started to fail on
some Core CI suites. So, it looks like the integration test setup may not
work in Core CI, at least in some suites.

Consider `ruby/irb` already has rather sophisticated test suite, I think
it's better to skip the integration tests in core CI for now.

https://github.com/ruby/irb/commit/6f49b4c108

[ruby/irb] Skip nested IRB tests in Ruby Core CI

2023-08-09T22:28:55+00:00

(https://github.com/ruby/irb/pull/675)

Sometimes the subprocess gets stuck in the nested IRB session until timed
out. We don't have enough information to debug it yet, so skip the tests
to unblock CI.

https://github.com/ruby/irb/commit/606f18c80c

[ruby/irb] Fix nested IRB sessions' history saving

2023-08-09T14:57:52+00:00

(https://github.com/ruby/irb/pull/652)

1. Dynamically including `HistorySavingAbility` makes things unnecessarily
   complicated and should be avoided.
2. Because both `Reline` and `Readline` use a single `HISTORY` constant
   to store history data. When nesting IRB sessions, only the first IRB
   session should handle history loading and saving so we can avoid
   duplicating history.
3. History saving callback should NOT be stored in `IRB.conf` as it's
   recreated every time `IRB.setup` is called, which would happen when
   nesting IRB sessions.

https://github.com/ruby/irb/commit/0fef0ae160