| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
Fix race condition in websocket stream write
|
| | |
|
|\ \
| | |
| | |
| | | |
Add a changelog entry for #25692
|
| | | |
|
|\ \ \
| | | |
| | | | |
[ci skip] Update documentation in AR SchemaStatements
|
|/ / /
| | |
| | |
| | | |
This includes minor grammar fixes throughout the file.
|
|\ \ \
| | | |
| | | | |
No need to set `cookie_only` option from Rails
|
| | | |
| | | |
| | | |
| | | | |
it false
|
|\ \ \ \
| | | | |
| | | | | |
Fix typo in test case
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Pathname might not be always initialized.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Require 'pathname' explicitly
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix typo: caches_pages to caches_page. [ci skip]
|
|/ / / / /
| | | | |
| | | | | |
Fix a small typo on doc: "caches_pages" -> "caches_page".
|
|\ \ \ \ \
| | | | | |
| | | | | | |
test with latest resque
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When run test of Active Job with resque 1.26, occurs following error.
```
QueuingTest#test_current_locale_is_kept_while_running_perform_later:
NoMethodError: undefined method `current_tags' for #<Resque::QuietFormatter:0x0055b44f63ed50>
/home/yaginuma/program/rails/master_y_yagi/rails/activejob/lib/active_job/logging.rb:51:in `logger_tagged_by_active_job?'
```
This was happening for the formatter class of resque not the formatter class of
Rails is they've been used to logger.formatter.
This was happening because become fomatter is changed during the instantiation
of worker in the resque 1.26.
In the master, unless the environment variable is set, fomatter is so as not to
be changed, test will pass.
Ref: https://github.com/resque/resque/pull/1439
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Don't reap connections that have already been reassigned
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This way, we aren't racing other threads, so we don't need to re-check
the conditional. And we no longer need to hold the lock while calling
remove (which can choose to make a new connection while we wait).
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A concurrent thread may have also detected it to be stale, and already
released (or even reassigned) it by now.
Fixes #25585
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A thread can only release a connection if it owns it, or it's owned by a
thread that has died.
|
|\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | | |
updating doc for prefer require_relative [ci skip]
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Correct defaults in documentation for ActionDispatch::SSL
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | | |
`config.ssl_options` permits configuring various options for the middleware. Default options for HSTS (specified with the `:hsts` key in the options hash) are specified in `.default_hsts_options`. The documentation did not make clear these defaults, and in one case was wrong.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
[ci skip] Update ConnectionPool documentation for readability purposes
|
| | |_|_|/ /
| |/| | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
[ci skip] Remove reference to Rails 4 in the initialization guide.
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Following commit removed reference to rails 4, but there is one left.
https://github.com/rails/rails/commit/a9f50f87c38659d0e9425f86f613cf5328d55d27
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Bump version for master bug report templates
|
| | | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
remove `-t` option from default sendmail arguments [ci skip]
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Follow up to #24436
|
|\ \ \ \ \
| | | | | |
| | | | | | |
`travel/travel_to` travel time helpers, now raise on nested calls
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
as this can lead to confusing time stubbing.
Instead of:
travel_to 2.days.from_now do
# 2 days from today
travel_to 3.days.from_now do
# 5 days from today
end
end
preferred way to achieve above is:
travel_to 2.days.from_now
# 2 days from today
travel_back
travel_to 5.days.from_now
# 5 days from today
Closes #24690
Fixes #24689
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
fledman/add_respond_to_missing_to_rails_application_configuration_custom
implement respond_to_missing? to match method_missing
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use `squish` rather than `strip_heredoc`
|
| | |_|_|/ / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
johnmeehan/allow-registering-directory-for-rake-notes
Allow rake notes to work with other directories.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
accidently set it to.
Made the change and test still passes.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Additional directories can be added using
SourceAnnotationExtractor::Annotation.register_directories("spec", "other_dir")
Result: rake notes will now extract notes from these directories.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Deprecate usage of nil as route path
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In Rails 4 these kind of routes used to work:
```ruby
scope '/*id', controller: :builds, as: :build do
get action: :show
end
```
But since 1a830cbd830c7f80936dff7e3c8b26f60dcc371d, routes are only created for
paths specified as strings or symbols. Implicit `nil` paths are just ignored,
with no deprecation warnings or errors. Routes are simply not created. This come
as a surprise for people migrating to Rails 5, since the lack of logs or errors
makes hard to understand where the problem is.
This commit introduces a deprecation warning in case of path as `nil`, while
still allowing the route definition.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Display railtie class name in `rails initializers`
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Add header demarcation to Action Cable guide
|