Closed
Bug 898543
Opened 11 years ago
Closed 11 years ago
Turn 'caching' logger up to ERROR in production
Categories
(Marketplace Graveyard :: Code Quality, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-08-20
People
(Reporter: oremj, Assigned: ashort)
Details
(Whiteboard: [qa-])
Right now messages like the following are about 25% of our total log entries: <amo.search.ES object at 0x78e5b50> cannot be cached. :/data/mkt.prod/www/marketplace.firefox.com/current/venv/lib/python2.6/site-packages/caching/base.py:277 I feel like these are not useful, and would like to discard them in production.
Reporter | ||
Comment 1•11 years ago
|
||
Alternatively, we can add "cache_key" or "query_key()" to those object or stop trying to cache them.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → ashort
Priority: -- → P1
Assignee | ||
Comment 2•11 years ago
|
||
https://github.com/washort/zamboni/commit/54093a2
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
Assignee | ||
Updated•11 years ago
|
Target Milestone: --- → 2013-08-13
Assignee | ||
Updated•11 years ago
|
Target Milestone: 2013-08-13 → 2013-08-20
You need to log in
before you can comment on or make changes to this bug.
Description
•