| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Previously Safari would try to load these files when you visit
localhost:3000. That created two exceptions in the log. It also caused
the exception notifier to send them out.
In response to #23427
|
|\
| |
| |
| |
| | |
prathamesh-sonpatki/improve-pg-version-old-error-message
Improve pg version old error message and mention this change in release notes.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Remove json gem dependency
|
|/ /
| |
| | |
All modern Rubies ship JSON as part of stdlib. Using the gem actually hurts multi-platform support due to build difficulties on Windows.
|
|\ \
| | |
| | | |
Put some space for non-assets requests in development mode
|
| |/
| |
| |
| | |
- Fixes #23428.
|
|\ \
| | |
| | | |
update supported version of PostgreSQL in docs [ci skip]
|
| | |
| | |
| | |
| | | |
Follow up to #23434
|
| | | |
|
|\ \ \
| | | |
| | | | |
use rails command in routes task
|
| |/ /
| | |
| | |
| | |
| | | |
For other task has become to use the rails command at doc and test,
I think that routes task also it is better to use the rails command.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
Changed id-writer to save join table records based on association
primary key #20995.
|
| | |
| | |
| | |
| | |
| | |
| | | |
key #20995
Changed id-writer to save join table records based on association primary key
|
| | |
| | |
| | |
| | |
| | | |
Prototype, you have served us well. But you are no longer how we make an
XMLHttpRequest. RIP
|
|\ \ \
| |_|/
|/| | |
Use rails secret command in guides
|
|/ / |
|
|\ \
| | |
| | | |
The minimum supported version of PostgreSQL is now >= 9.1
|
|/ / |
|
|\ \
| | |
| | | |
Fix typo.
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Several ActionCable doc fixes
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
* Properly indent code sample in ActionCable::Channel::Streams
* Add a doc comment for #stop_all_streams
* Reformat + add <tt> blocks around code references in ActionCable::Base docs
* Clarify and a little better grammar on ActionCable::RemoteConnections
* Correct indentation and clean up ActionCable::Server::Broadcasting code sample
|
| |
| |
| |
| | |
There was a typo in the variable name leading to infinite recursion
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We had previously updated this to attempt to map over whatever was
passed in, so that additional types like range and array could benefit
from this behavior without the time zone converter having to deal with
every known type.
However, the default behavior of a type is to just yield the given value
to `map`, which means that if we don't actually know how to handle a
value, we'll just recurse infinitely. Since both uses of `map` in this
case occur in cases where we know receiving the same object will
recurse, we can just break on reference equality.
Fixes #23241.
|
|\ \
| | |
| | | |
Remove unnecessary overriding of `#initialize`
|
| | |
| | |
| | |
| | |
| | |
| | | |
`#initialize` of `HasManyReflection`, `HasOneReflection` and
`BelongsToReflection` only pass all arguments to `super` by passed order.
These overriding can be removed.
|
|\ \ \
| |/ /
|/| | |
Change command_task.rb to commands_task.rb in docs
|
|/ /
| |
| | |
The initialization documentation references `rails/commands/command_task.rb`. This appears to be a typo as the file is actually `rails/commands/commands_task.rb`.
|
|\ \
| | |
| | | |
Warn if a named scope is overwriting an existing scope or method
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit f6db31ec16e42ee7713029f7120f0b011d1ddc6c.
Reason:
Scope names can very easily conflict, particularly when sharing Concerns
within the team, or using multiple gems that extend AR models.
It is true that Ruby has the ability to detect this with the -w option, but the
reality is that we are depending on too many gems that do not care about Ruby
warnings, therefore it might not be a realistic solution to turn this switch on
in our real-world apps.
|
|\ \ \
| | | |
| | | | |
move `test_generator_if_skip_action_cable_is_given_for_an_api_app` to the appropriate file
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
appropriate file
Test of Rails API should be in `api_app_generator_test.rb`.
|
|\ \ \ \
| | | | |
| | | | | |
Duplicate assert_generates options before modifying it
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix regression in `Hash#dig` for HashWithIndifferentAccess.
|
|/ / / / / |
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Generated engines should call `protect_from_forgery`. If this method
isn't called, then the Engine could be susceptible to XSS attacks.
Thanks @tomekr for reporting this to us!
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Update CHANGELOG.md
|
|/ / / /
| | | |
| | | | |
fix indentation to show it as code
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
And improve changelongs.
[ci skip]
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix corrupt transaction state caused by `before_commit` exceptions
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a `before_commit` callback raises, the database is rolled back but
AR's record of the current transaction is not, leaving the connection in
a perpetually broken state that affects all future users of the
connection: subsequent requests, jobs, etc. They'll think a transaction
is active when none is, so they won't BEGIN on their own. This manifests
as missing `after_commit` callbacks and broken ROLLBACKs.
This happens because `before_commit` callbacks fire before the current
transaction is popped from the stack, but the exception-handling path
they hit assumes that the current transaction was already popped. So the
database ROLLBACK is issued, but the transaction stack is left intact.
Common cause: deadlocked `#touch`, which is now implemented with
`before_commit` callbacks.
What's next:
* We shouldn't allow active transaction state when checking in or out
from the connection pool. Verify that conns are clean.
* Closer review of txn manager sad paths. Are we missing other spots
where we'd end up with incorrect txn state? What's the worst that can
happen if txn state drifts? How can we guarantee it doesn't and
contain the fallout if it does?
Thanks for @tomafro for expert diagnosis!
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Solves personal insanity, since I was down in these files.
(Please don't submit PRs like this.)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some places were saying filter, while others said filter_options, spare the ambiguity
and use filter throughout.
This inlines a needless local variable and clarifies a route filter consists of defaults
and values to match against.
|