ActiveSupport expects a hash as a payload for notifications #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ActiveSupport expects a hash to be passed as the payload to
instrument
. In the majority of cases, not passing a hash doesn't cause any incorrect behaviour.However, if the block passed to
instrument
raises an Exception, ActiveSupport::Notifications will attempt to add an:exception
key to the payload hash. When this occurs within a cache fetch for ReadThis, the end result is aTypeError
from deep inside the cache code, unrelated to the original exception. (https://github.com/rails/rails/blob/30af171af13293aa37bee612ae7b976d3ede0439/activesupport/lib/active_support/notifications.rb#L64)(credit goes to @banister for figuring out this edge case)