Dont swallow errors when bad alias_method
Fix rational to decimal on type_cast_from_user
Change class evaluation for Rationals in cast_value
Fix case statement to use ::Numeric and ::String
Fix decimal_test module and add new test for object responding to to_d
pass the route name to define_url_helper

this allows us to avoid 2 hash allocations per named helper definition,
also we can avoid a `merge` and `delete`.
`recall` should be `path_parameters`, also make it required

"recall" is a terrible name.  This variable contains the parameters that
we got from the path (e.g. for "/posts/1" it has :controller => "posts",
:id => "1").  Since it contains the parameters we got from the path,
"path_parameters" is a better name.  We always pass path_parameters to
`generate`, so lets make it required.
[EXPERIMENTAL] run actionpack tests in parallel

only on forking systems though.  Feel free to revert this if it causes
problems.
Merge pull request #16188 from marianovalles/fix_rational_to_decimal_type_cast

Fix rational to decimal on type_cast_from_user
Prefer if/else for this case

One of the branches is using a proc to check if the value respond_to a
method so it is better to not do case comparations
Disable some tests on SQLite

These tests were passing before because the precision were not using to
cast the value. Not it is being used so it would fail on sqlite3
only parallelize on forking systems
do not restart the service, just stop it
fix filesystem race condition
check for valid options in validate method

This change prevents a certain class of user error which results when
mistakenly using the `validate` class method instead of the `validates`
class method.

Only apply when all arguments are symbols, because some validations use
the `validate` method and pass in additional options, namely the
`LenghValidator` via the `ActiveMode::Validations::validates_with`
method.
Merge pull request #16210 from sonnym/assert_valid_keys_in_validate

Check for valid options in validate method
pass the test reporter by reference

this prevents the array from being dumped as a DRbObject so we can
reduce communication with the server.  the reporter should always exist
on the server side, so we don't have to worry about GC
fix thread safety issues

this test case had a race condition where it could download data
multiple times.  We'll download the data once at class load.
%i doesn't work on 1.9
reporting is only done in one thread, so we can safely remove the lock

(I think)