| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Grammar fixes based on pass over ETag doc changes
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| |/
|/| |
remove deprecated `datetime_field` from guide [ci skip]
|
|/
|
|
| |
`datetime_field` was deprecated in 316811b4d3f4e5a1a7bcd03de97c67218770e333
|
|\
| |
| | |
Remove not needed including
|
| |
| |
| |
| |
| | |
Because `DateTime` inherits `Date` and `Date` includes `DateAndTime::Zones`,
`DateTime` not need to include `DateAndTime::Zones` again.
|
|\ \
| |/
|/| |
Grammer fix in comment: capitalize first word in sentence [ci skip].
|
|/ |
|
|\
| |
| | |
Strong ETag validators
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Introduce `Response#strong_etag=` and `#weak_etag=` and analogous options
for `fresh_when` and `stale?`. `Response#etag=` sets a weak ETag.
Strong ETags are desirable when you're serving byte-for-byte identical
responses that support Range requests, like PDFs or videos (typically
done by reproxying the response from a backend storage service).
Also desirable when fronted by some CDNs that support strong ETags
only, like Akamai.
* No longer strips quotes (`"`) from ETag values before comparing them.
Quotes are significant, part of the ETag. A quoted ETag and an unquoted
one are not the same entity.
* Support `If-None-Match: *`. Rarely useful for GET requests; meant
to provide some optimistic concurrency control for PUT requests.
|
|\ \
| |/
|/| |
Fixes broken link in 'Ruby on Rails 2.2 Release Notes'
|
|/ |
|
|\
| |
| | |
sanitiser helper may be remove in 5.1, update doc [ci skip]
|
| |
| |
| | |
using `rails-html-sanitizer` gem still Rails providing strip_tags, strip_links features. May be remove in 5.1
|
| |
| |
| |
| |
| |
| | |
This reverts commit 7b82e1c77b48cb351da4e0ed6ea0bac806d4925c.
This would have removed the ability to reference a schema when using PG
|
|\ \
| | |
| | | |
Fix method String#upcase_first
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | | |
kamipo/move_quoted_names_cache_up_to_abstract_adapter
Move `@quoted_{column|table}_names` cache up to the abstract adapter
|
| |/ |
|
|\ \
| | |
| | | |
Deprecate `datetime_field` and `datetime_field_tag` helpers.
|
| |/
| |
| |
| |
| | |
Datetime input type was removed from HTML specification.
One can use `datetime_local_field` and `datetime_local_field_tag` instead.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When prepared statements are enabled, the statement cache caches the SQL
directly, including the bind parameters. If a similar query is run later
with prepared statements disabled, we need to use a separate cache
instead of trying to share the same one.
Fixes #24351
|
| |
| |
| |
| |
| |
| |
| |
| | |
Dots have special meaning in most backends (e.g. everything except
SQLite3), as well as most methods that work with table or column names.
This isn't something that we ever explicitly supported, but there's at
least one case of somebody using this (see #24367), so we'll go through a deprecation
cycle as normal.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This issue occured because associations now call `where` directly, and a
dot in the key name for `where` means nested tables. For this fix, we
now pass the table name as a symbol, and do not attempt to expand
symbols containing a dot.
This is a temporary fix. I do not think we should support table names
containing a dot, as it has a special meaning in most backends, as well
as most APIs that involve table names. This commit does not include a
test, as I am going to deprecate table names containing dots in the
following commit.
Fixes #24367
|
|\ \
| | |
| | | |
[ci skip] Parameters filter performs regular expression partial matching
|
|/ / |
|
|\ \
| | |
| | | |
Cable message encoding
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Introduce a connection coder responsible for encoding Cable messages
as WebSocket messages, defaulting to `ActiveSupport::JSON` and duck-
typing to any object responding to `#encode` and `#decode`.
* Consolidate encoding responsibility to the connection. No longer
explicitly JSON-encode from channels or other sources. Pass Cable
messages as Hashes to `#transmit` and rely on it to encode.
* Introduce stream encoders responsible for decoding pubsub messages.
Preserve the currently raw encoding, but make it easy to use JSON.
Same duck type as the connection encoder.
* Revert recent data normalization/quoting (#23649) which treated
`identifier` and `data` values as nested JSON objects rather than as
opaque JSON-encoded strings. That dealt us an awkward hand where we'd
decode JSON strings… or not, but always encode as JSON. Embedding
JSON object values directly is preferably, no extra JSON encoding,
but that should be a purposeful protocol version change rather than
ambiguously, inadvertently supporting multiple message formats.
|
|\ \
| |/
|/| |
Cable: reconcile default worker pool size with low db conn pool size
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Whack it down from 100 to 4.
Large worker pools means large db connection counts. We aren't set up
for that by default and most apps won't need it out of the box.
We're better off tuning the default worker pool for low traffic, low
resource consumption apps. Those who have higher traffic will scale up
to meet demand.
|
|\ \
| | |
| | | |
Make to private the visibility of `_quote` and `_type_cast`
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Replace _meth with _method to remove ambiguity
|
|/ /
| |
| |
| | |
[ci skip]
|
|\ \
| | |
| | | |
Update Gemfile.lock
|
| | |
| | |
| | |
| | |
| | | |
'rake' gem is bundled to '>= 11.1' by 30279704646fff33e64c71ee3c4de34bf75232c4
(#23499), but it seems the commit did not fully include Gemfile.lock's.
|
|\ \ \
| |/ /
|/| | |
Suppress warnings
|
|/ /
| |
| |
| |
| | |
"Using a dynamic :controller (or :action) segment in a route is deprecated"
by 6520ea5f7e2215a763ca74bf6cfa87be2347d5df (#23980).
|
|\ \
| | |
| | | |
provide file name for fixture ERB
|
| | | |
|
|\ \ \
| | | |
| | | | |
Run one JRuby worker on CI; allow to fail
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Uses latest precompiled JRuby so that
we don't spend time downloading versions Travis has
not already compiled. http://rubies.travis-ci.org/
Uses latest jdk: oraclejdk8
per
https://docs.travis-ci.com/user/build-environment-updates/2015-02-03/#Ruby-VM
and
https://docs.travis-ci.com/user/languages/ruby/#Supported-Ruby-Versions-and-RVM
Follows on work in https://github.com/rails/rails/pull/23927 which was reverted
https://github.com/rails/rails/commit/26fe5fa08d52384bcea09c4210e3b3baaf5e9b95
JRUBY_OPTS minimize GC, disable JIT, for max test speed
- https://github.com/rails/rails/pull/16613
- https://github.com/rails/rails/pull/17088
Have Rails use JRuby-compatible Rake 11.1
- The Rake task was passing --verbose, an invalid option, to contemporary JRuby
- https://github.com/ruby/rake/pull/120
- https://github.com/rails-api/active_model_serializers/pull/1585
- https://github.com/jruby/jruby/issues/3653#issuecomment-195883717
No advantage to directly mounting JRuby over installing from cache; both on S3
- https://github.com/rails/rails/pull/23499/commits/b2d5b336b5a812009444571b22eed90777cd9a8c
- https://github.com/rails/rails/pull/23499/commits/f4fad041b2755d81e82ee3fc66d96f334b4653db
|
|\ \ \ \
| | | | |
| | | | | |
Pass over CHANGELOGs [ci skip]
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Fix rails restart issue with Puma
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- We need to pass the restart command to Puma so that it will use it
while restarting the server.
- Also made sure that all the options passed by user while starting
the server are used in the generated restart command so that they will
be used while restarting the server.
- Besides that we need to remove the server.pid file for the previous running
server because otherwise Rack complains about it's presence.
- We don't care if the server.pid file does not exist. We only want to delete
it if it exists.
- This also requires some changes on Puma side which are being tracked
here - https://github.com/puma/puma/pull/936.
- Fixes #23910.
|
|\ \ \ \
| | | | |
| | | | | |
Fix deprecation warning for ParamsParser instance :smile:
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Related with 38d2bf5fd1f3e014f2397898d371c339baa627b1.
cc @tenderlove
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Add upcase_first method
|