This project is archived and is in readonly mode.
"Cached fragment hit" written to log even if fragment is not cached
Reported by Erik Andrejko | July 16th, 2009 @ 05:48 PM
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.
Comments and changes to this ticket
-
Michael Koziarski August 3rd, 2009 @ 06:14 AM
- Tag changed from actioncontroller, actionpack, caching, patch to actioncontroller, actionpack, bugmash, caching, patch
-
dira August 8th, 2009 @ 03:00 PM
verified
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 August 8th, 2009 @ 04:40 PM
+1
Patch applied cleanly to edge with --whitespace=fix option as @dira said. All tests passing.
-
Repository August 8th, 2009 @ 04:47 PM
- State changed from new to resolved
(from [efcfce50c417975ee038a107755a1542a690d39b]) Fixes "Cached fragment hit" written to log even if fragment is not cached (Erik Andrejko) [#2917 state:resolved] http://github.com/rails/rails/commit/efcfce50c417975ee038a107755a15...
-
CancelProfileIsBroken August 8th, 2009 @ 11:08 PM
- Tag changed from actioncontroller, actionpack, bugmash, caching, patch to actioncontroller, actionpack, caching, patch
- Milestone cleared.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Attachments
Referenced by
- 2917 "Cached fragment hit" written to log even if fragment is not cached (from [efcfce50c417975ee038a107755a1542a690d39b]) Fixes "...