Steven Willis

For some background as to why we'd want custom tasks to be loaded for `bin/rails test`: We do some important setup in `test/test_helper.rb` that we always want to run before...

[One of the comments](https://github.com/rails/rails/issues/27088#issuecomment-261385679) on #27088 said: > Right now it is not possible to extend the rails commands, so you are not able to add dependencies to the rails...

By the way, when I was adding tests, I tried to follow the pattern of the other tests in `TestTimestampParser` by calling `date.get_date_from_timestamp` directly, and passing in a custom value...

@Gallaecio Is this good to merge?

The examples in the added tests should show the issue. You could try running those tests on the main line code without my changes. > But if we are applying...

> Where do we see that behavior, since the apply_tiemzone_from_settings would apply the timezone from the settings, I believe? Yes, but with the new code, the naive datetime object is...

Here's an example. With the current code: ``` >>> dateparser.parse('1661996156', settings={'TIMEZONE': 'UTC', 'TO_TIMEZONE': 'UTC', 'RETURN_AS_TIMEZONE_AWARE': True}).timestamp() 1661981756.0 ``` The returned unix timestamp doesn't match the original timestamp. And with my...

@gutsytechster @Gallaecio I think everything has been resolved, can it be merged?

This also happens if you try to use [Apple's App Store Connect OpenAPI spec](https://developer.apple.com/sample-code/app-store-connect/app-store-connect-openapi-specification.zip). They have parameters for controlling the sorting of returned data, and to sort in reverse you...

This is unrelated to the issue, but running `rails app:update` also changes the active job queue name: ``` # Use a real queuing backend for Active Job (and separate queues...