- ### Problem

  ActionPack requires "action_view/base" at boot time, this
  causes a variety of issue that I described in detail in #38024.

  There is no real reason to require av/base in the
  ActionDispatch::Debugexceptions class.

  ### Solution

  Like any other components (such as ActiveRecord, ActiveJob...),
  ActionView::Base shouldn't be loaded at boot time.

  Here are the two main changes needed for this:

  1) Actionview has a special initializer that needs to run
     before the app is fully booted (adding a executor needs to be done
     before application is done booting)
  https://github.com/rails/rails/blob/63ec70e700e321b22e9baf2ad2d45cd3f4febc79/actionview/lib/action_view/railtie.rb#L81-L84

     That initializer used a lazy load hooks but we can't do that anymore
     because Action::Base view won't be triggered during booting process.
     When it will get triggered, (presumably on the first request),
     it's too late to add an executor.

  ------------------------------------------------

  2) Compare to other components, ActionView doesn't use `Base` for
     configuration flag. A lot of flags ares instead set on modules
     (FormHelper, FormTagHelper).
     The problem is that those module depends on AV::Base to be
     loaded, as otherwise configuration set by the user aren't applied.
     (Since the lazy load hooks hasn't been triggered)
     https://github.com/rails/rails/blob/63ec70e700e321b22e9baf2ad2d45cd3f4febc79/actionview/lib/action_view/railtie.rb#L66-L69

     We shouldn't wait for AB::Base to be loaded in order to set these
     configuration. However, we need to do it inside an
     `after_initialize` block in order to let application
     set it to the value they want.

  Closes #28538

  Co-authored-by: betesh <iybetesh@gmail.com>"

Api-docs validation defaults missing absence [ci skip]

unify puma types and remove blocks

Address `Error: caskroom/cask was moved. Tap homebrew/cask-cask instead`

This error message suggests using `tap homebrew/cask-cask`,
actually it does not work, refer "FYI - `tap homebrew/cask-cask` cause this error:" below.

* Without this change:
```
$ brew bundle
Using homebrew/core
Using homebrew/bundle
Using homebrew/services
Error: caskroom/cask was moved. Tap homebrew/cask-cask instead.
Tapping caskroom/cask has failed!
```

* With this change:
```
$ brew bundle
Using homebrew/core
Using homebrew/bundle
Using homebrew/services
Tapping homebrew/cask
Installing ffmpeg
Installing memcached
Installing mysql
Installing postgresql
Installing redis
Installing yarn
Password:
Installing xquartz
Installing mupdf
Installing poppler
Installing imagemagick
Homebrew Bundle complete! 14 Brewfile dependencies now installed.
$
```

* FYI - `tap homebrew/cask-cask` cause this error:

```
$ brew bundle
Using homebrew/core
Using homebrew/bundle
Using homebrew/services
Username for 'https://github.com': yahonda
Password for 'https://yahonda@github.com':
==> Tapping homebrew/cask-cask
Cloning into '/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-cask'...
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/Homebrew/homebrew-cask-cask/'
Error: Failure while executing; git clone https://github.com/Homebrew/homebrew-cask-cask /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-cask --depth=1 exited with 128.
Tapping homebrew/cask-cask has failed!
```

Remove `:connection_id` in an internal instrument

Without this, `Rails.application` returns `nil`.
Ref: https://buildkite.com/rails/rails/builds/65683#e86ec58e-53a5-41be-8aeb-11c5705ee580/1042-1053

Seems that is the reason not to work code highlight.

This broke the markup.

Related #36456.

I grepped the code base by `git grep -n 'connection_id: '` then I found
extra `connection_id: object_id` which is added at #20818 but unused.

Actually the `connection_id: object_id` is not a connection's object_id
but a connection_handler's object_id, it is very confusing.

Since the `:connection_id` in an internal instrument is not used, we can
just remove the incorrect information.

[Railties] Add config rake_eager_load

Update instructions in generated Postgresql database.yml.

Delegate child session assertions to parent session

Some code examples were missing the language used for code highlighting.

Add backend API doc for action text [ci skip]

Remove call to object_id

minor grammar fix

Update documentation to explain the behavior of explicitly raising ActiveRecord::Rollback in a nested transaction [skip ci]

Add some examples for getting current_user

Remove `spring-watcher-listen` from default Gemfile

Reversible remove_columns

Update The Rails Initialization Process page[ci skip]

Fix FrozenError on ActiveModel::Error clear and delete

Update downloading section

Respect Content-Type header passed in head method

Move `name` key on configuration hash into `DatabaseConfig`

Update .yardopts to document *.rb files in [GEM]/app

`name` is used by Rails to find the configuration by connection
specification name, but database adapters don't need to use `name` in
order to establish a connection. This is part of our work to separate
what the database needs to connect (the configuration hash) and the
what Rails needs to find connections (everything else).
Co-authored-by: NJohn Crepezzi <john.crepezzi@gmail.com>

Also close PRs with no activity over 3 months

Make `belongs_to_required_by_default` a class attribute:

* Add failing ActiveJob exceptions test for "disable retry jitter"

Thanks to @kaspth for the starting point.

* Update ActiveJob retry jitter to correctly use zero value

* Simplify "disable retry jitter" test

We don't need to repeat this many times. Fewer is shorter.

* Refactor determine_delay with jitter

* Fix indentation

* Close the curtains and give JITTER_DEFAULT some privacy

* Use .zero? instead of == to check jitter value

* Add ActiveJob test for explicit zero jitter
Co-authored-by: NKasper Timm Hansen <hey@kaspth.com>
Co-authored-by: NCliff Pruitt <cliff.pruitt@cliffpruitt.com>

- I'm hoping to get this change accepted even though this flag was
  introduced years ago in 6576f735

  My use case is the following:

  We were never enforcing belongs to association and we have a lot
  of models that implicitely declare an association as optional.
  We are now changing all our models to make associations required
  by default.
  Since we have a lot of models (more than 1000), I'd like to
  progressively enable them to use the `belongs_to_required_by_default`
  flag.

  The problem is that this flag is a mattr_accessor and doesn't to be
  set per model. We basically need to modify all our models (which
  could take years) before being able to modify the global flag.

  I'd like to change this flag to a class_attribute to solve the
  issue.

Deprecate `connection_config`

Rename a test method to not conflict with a deprecated method

This method in test has a confusing name that also is the same as a
method with a different behavior on `ActiveRecord::Base` so we're just
renaming it to avoid confusion between the two!
Co-authored-by: Neileencodes <eileencodes@gmail.com>