Followup to e7514dc6.

Ignore Errno::ENOTEMPTY when calling AS::Cache::FileStore#clear with race conditions

Load XML Builder if it is not available

Update the Rails mailing list URLs to new discuss discourse URL

Restore the `lookup_store` compatibility to accept config as a single object

9845cd63 broke configuring a cache store like so:

    config.cache_store = :redis_cache_store, config_for("redis/cache")

Rails::Application#config_for returns an ActiveSupport::OrderedOptions. By default, the Array#extract_options! core extension won't extract instances of Hash subclasses. Add ActiveSupport::OrderedOptions#extractable_options? and have it return true to fix.

Closes #37435.

This fixes a regression #38532 caused by f9633cd0.

Closes #38532.

This reverts commit 7aa047b5, reversing
changes made to c9b36dd6.

This is a right example for singular names.

Fix IRB deprecation warning on tab-completion on Ruby <= 2.5:

Fix IRB deprecation warning on tab-completion

Fix CI error with minitest 5.14

https://github.com/seattlerb/minitest/commit/5802aa08280a3609b684e0ebef95dabfbd3ec9ff
https://github.com/seattlerb/minitest/pull/809#discussion_r332399750

To support both 5.13.0 and 5.14.0, use `#initialize` instead.

https://buildkite.com/rails/rails/builds/66168#b348f446-0406-425e-ba53-c5d15034cf98/1002-1070

Return unfrozen strings from to_sentence

Make `LoadInterlockAwareMonitor` work in Ruby 2.7

Distinguish missing controller exceptions from unrelated NameError

Use new `...` syntax in Module#delegate if it's available

number_to_currency negative zero fix

Co-authored-by: NChristian Gregg <c_arlt@hotmail.com>

When `ActiveSupport.parse_json_times` is `true`,
`ActiveSupport::Messages::Medata.verify` will fail with a `TypeError` as
it does not pass a `String` to `Time.iso8601` as is expected.

This leads to hard-failure on retrieval of signed cookies with expiries.

since RedisCacheStore#write_entry takes kwargs, we needed to kwargsify all these methods
in order to eliminate Ruby 2.7 warnings.

It's a little bit bigger patch than I expected, but it doesn't warn on Ruby 3,
and it doesn't introduce any incompatibility on loder rubies, so it may not be a bad thing anyway.