This project is archived and is in readonly mode.
New default backtrace filter for Gems
Reported by Juan Lupión | November 30th, 2008 @ 01:17 PM | in 2.x
The attached patch will leverage the new backtrace filters to pretty print gem versions on the logs, as shown here: http://gist.github.com/30430
Comments and changes to this ticket
-
porras December 8th, 2008 @ 12:12 AM
- Tag changed from backtrace, edge, logging, patch to backtrace, edge, logging, patch, verified
+1
-
josh December 8th, 2008 @ 04:52 AM
- Assigned user set to DHH
- State changed from new to open
Pretty cool
-
Repository December 15th, 2008 @ 02:38 PM
- State changed from open to committed
(from [f9a02b12d15bdbd3c2ed18b16b31b712a77027bc]) Added gem backtrace pretty priting (Juan Lupión) [#1497 state:committed] http://github.com/rails/rails/co...
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
- 1497 New default backtrace filter for Gems (from [f9a02b12d15bdbd3c2ed18b16b31b712a77027bc]) Added g...
- 2141 Correctly clean backtraces from vendor/gems and alternate gem installation directories Improvement on the idea in #1497.