mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
✂️
[ci skip]
This commit is contained in:
parent
81abcb7947
commit
016eb65d7e
2 changed files with 5 additions and 5 deletions
|
@ -11,7 +11,7 @@ require 'active_support/time'
|
|||
require 'active_support/json'
|
||||
|
||||
class MessageVerifierTest < ActiveSupport::TestCase
|
||||
|
||||
|
||||
class JSONSerializer
|
||||
def dump(value)
|
||||
ActiveSupport::JSON.encode(value)
|
||||
|
@ -21,7 +21,7 @@ class MessageVerifierTest < ActiveSupport::TestCase
|
|||
ActiveSupport::JSON.decode(value)
|
||||
end
|
||||
end
|
||||
|
||||
|
||||
def setup
|
||||
@verifier = ActiveSupport::MessageVerifier.new("Hey, I'm a secret!")
|
||||
@data = { :some => "data", :now => Time.local(2010) }
|
||||
|
@ -43,7 +43,7 @@ class MessageVerifierTest < ActiveSupport::TestCase
|
|||
assert_not_verified("#{data}--#{hash.reverse}")
|
||||
assert_not_verified("purejunk")
|
||||
end
|
||||
|
||||
|
||||
def test_alternative_serialization_method
|
||||
prev = ActiveSupport.use_standard_json_time_format
|
||||
ActiveSupport.use_standard_json_time_format = true
|
||||
|
@ -54,7 +54,7 @@ class MessageVerifierTest < ActiveSupport::TestCase
|
|||
ensure
|
||||
ActiveSupport.use_standard_json_time_format = prev
|
||||
end
|
||||
|
||||
|
||||
def assert_not_verified(message)
|
||||
assert_raise(ActiveSupport::MessageVerifier::InvalidSignature) do
|
||||
@verifier.verify(message)
|
||||
|
|
|
@ -775,7 +775,7 @@ error similar to given below will be thrown.
|
|||
ActiveRecord::ConnectionTimeoutError - could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it:
|
||||
```
|
||||
|
||||
If you get the above error, you might want to increase the size of connection
|
||||
If you get the above error, you might want to increase the size of connection
|
||||
pool by incrementing the `pool` option in `database.yml`
|
||||
|
||||
NOTE. If you have enabled `Rails.threadsafe!` mode then there could be a chance that several threads may be accessing multiple connections simultaneously. So depending on your current request load, you could very well have multiple threads contending for a limited amount of connections.
|
||||
|
|
Loading…
Reference in a new issue