This project is archived and is in readonly mode.
"Cached fragment hit" written to log even if fragment is not cached
When using the <% cache(...) do %> ... <% end %> idiom within a view a "Cached fragment hit" line will be written to the log even in the case that the fragment is not actually cached. This behavior is misleading.
-
caching_log_messages.patch
1.68 KB
-
Michael Koziarski- Tag changed from actioncontroller, actionpack, caching, patch to actioncontroller, actionpack, bugmash, caching, patch
-
diraverified
Test & patch apply cleanly with
git apply --whitespace=fix
Trying to run the test to see it failing without the fix will correctly give a failure, even if the message is unintuitive (a mocha bug).
-
David Trasbo+1
Patch applied cleanly to edge with --whitespace=fix option as @dira said. All tests passing.
-
Repository- State changed from new to resolved
(from [efcfce50c417975ee038a107755a1542a690d39b]) Fixes "Cached fragment hit" written to log even if fragment is not cached (Erik Andrejko) [#2917 "Cached fragment hit" written to log even if fragment is not cached state:resolved] http://github.com/rails/rails/commit/efcfce50c417975ee038a107755a15...
-
CancelProfileIsBroken
- Tag changed from actioncontroller, actionpack, bugmash, caching, patch to actioncontroller, actionpack, caching, patch
- Milestone cleared.