A thread can only release a connection if it owns it, or it's owned by a
thread that has died.

Add ActiveSupport::Notifications hook to ActionCable::Server.broadcast

ActionCable, sometimes add_channel is not called.

Improve error message when record touch fails.

Clarify Postgres initials. [skip ci]

Update Rails 5 release notes with syntax fixes. [ci skip]

The current error message only indicates that a touch can fail because the record is new. In practice, we saw cases where touches were failing because the record had been destroyed. `persisted?` checks `new_record?` *and* `destroyed?`. It was confusing to get a message about a new record when in reality we were destroying records.

I also included a helpful tip for users to consider using `persisted?`, `new_record?`, or `destroyed?` before touching.

Fix typo: accidently -> accidentally. [ci skip]

remove needless comments

Correct guide generation command [ci skip]

Remove unused `predicate_builder` for `BasicObjectHandler` and `RangeHandler`

`partial` option on the digest method is no more needed [ci skip]:

refer to rails command instead of rake in doc of `SourceAnnotationExtractor`

Clean backtrace in IRB

- `partial` option is not used anymore, this was removed in https://github.com/rails/rails/pull/23724

fix task name to remove

Follow up to #25431

Remove #select_one from Mysql2Adapter

Renamed NestedParametersTest to NestedParametersPermitTest

Revert "Rename `active_record_internal_metadatas` to `ar_internal_metadata"

Remove `create_table_info_cache` because it not be reused

Since bundler 1.12.0, the gemspec is validated so the `bundle install`
command will fail just after the gem is created causing confusion to the
users. This change was a bug fix to correctly validate gemspecs.

Do not depend on Rails git repository layout in ActiveSupport tests.

Pass `pk: false` to `connection.insert` explicitly if do not have a primary key

- Cleaned up backtrace cleaner test code and removed instaces variables

Add handling of cleaning up backtrace from IRB console in case of errors

ActionDispatch::DebugLocks

Don't inherit from Concurrent::CountDownLatch

close hijacked i/o socket after use (fixes #25613)

When an exception is raised, those Action View rendering logs are just
noise for the end developer. I recently silenced those from Web Console,
as we do use Action View rendering in it as well. It used created a half
a screen of rendering logs. I think we can save those in this recent
push for cleaner development logs.

Now, the silencing is a bit hacky and we have a bunch of it now, so we
can also invest in turning off the logs directly from Action View
objects instead of silencing off the logging stream.