rake log:clear task updated 

It might be tough for readers to know why we implement `===`, and where
the Regexp in `derive_regexp` came from.

The line filter parsing added to ActiveSupport::TestCase is only half the story
to enable line filtering. The other half, of adding the patterns to the options,
is done in the Minitest plugin that Railties has.

Thus it makes more sense to have the filter in Railties with the other half and
all the line filtering tests.

Move the filter and extend Active Support in an initializer, so that when users
or `rails/all.rb` require `rails/test_unit/railtie` we can still filter by line.

match the environment variable name that actually checking and error message

- Avoided truncating all files if no ENV['LOGS'] specified
- Updated task to accept LOGS=all for truncating all files from log/ i.e. log/*log
- If no LOGS specified will truncates standard environment log files i.e. 'development,test,production'
- CHANGELOG & guide update added
- bin/setup test cases fixed

[ci skip] `automatic_inverse_of` returns `false` not `nil` (document …

The error message has become a `DISABLE_DATABASE_ENVIRONMENT_CHECK`, modified to match the error message.

ref: https://github.com/rails/rails/blob/master/activerecord/lib/active_record/migration.rb#L161

Merge pull request #22987 from prathamesh-sonpatki/add-missing-changelong-for-schema-migrations-version

Added missing CHANGELOG entry for https://github.com/rails/rails/pull/22976

[ci skip]

Get update_attributes working with SchemaMigration

This is really strange, as it passes on Travis for 2.3, and it passes
for me locally on 2.2. But on travis w/ 2.2, passing `Float::INFINITY`
in is resulting in an infinite loop. This should resolve it.

[ci skip] Fix typo Renderering --> Rendering

This is an alternate implementation to #22875, that generalizes a lot of
the logic that type decorators are going to need, in order to have them
work with arrays, ranges, etc. The types have the ability to map over a
value, with the default implementation being to just yield that given
value. Array and Range give more appropriate definitions.

This does not automatically make ranges time zone aware, as they need to
be added to the `time_zone_aware` types config, but we could certainly
make that change if we feel it is appropriate. I do think this would be
a breaking change however, and should at least have a deprecation cycle.

Closes #22875.

/cc @matthewd

Prevent destructive action on production database

You cannot use `update_attributes` on models that do not have a primary key. Since SchemaMigration versions are guaranteed to be unique (they have a unique index on them) we can safely use them as a primary key.

Revert "Move async execution from celluloid to concurrent-ruby"

Move async execution from celluloid to concurrent-ruby

Discussion: https://github.com/rails/rails/pull/22967#discussion_r49137035

Raise an error when a destructive action is made on a database where the current environment is different from the environment stored in the database.

but rather very often used inside helpers to directly return a String value.
[ci skip]

Fix `select_values` method signature for consistency

`{update|delete}_sql` are almost the same as `{update|delete}`

Fix typo in ActionPack CHANGELOG [ci skip]

Simply `{update|delete}_sql` aliases to `{update|delete}`.

This PR introduces a key/value type store to Active Record that can be used for storing internal values. It is an alternative implementation to #21237 cc @sgrif @matthewd.

It is possible to run your tests against your production database by accident right now. While infrequently, but as an anecdotal data point, Heroku receives a non-trivial number of requests for a database restore due to this happening. In these cases the loss can be large.

To prevent against running tests against production we can store the "environment" version that was used when migrating the database in a new internal table. Before executing tests we can see if the database is a listed in `protected_environments` and abort. There is a manual escape valve to force this check from happening with environment variable `DISABLE_DATABASE_ENVIRONMENT_CHECK=1`.

Match HashWithIndifferentAccess#default & Hash#default

Fix changelog for per-form CSRF tokens

While the option on `ActiveRecord::Base` is always around, we need to
explicitly set it on the config object. Otherwise the recommended
configuration change results in an error.

Fixes #22839