Closed
Bug 1236592
Opened 8 years ago
Closed 8 years ago
Update pylibmc to v1.5.0 and django-pylibmc to v0.6.1
Categories
(Tree Management :: Treeherder, defect, P2)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Attachments
(1 file)
Prior to making stage/prod use django-pylibmc / pylibmc for parity with Heroku (in bug 1182043), we should update the Heroku-specific requirements file so we're on the latest versions of them.
Comment 1•8 years ago
|
||
Comment 2•8 years ago
|
||
Commits pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/f0395a3cd64acee3510299f62a7b67905570f89a Bug 1236592 - Heroku: Update pylibmc from v1.4.2 to v1.5.0 One of the most notable changes is a fix for a few memory leaks. http://sendapatch.se/projects/pylibmc/changelog.html https://github.com/lericson/pylibmc/compare/1.4.2...1.5.0 https://github.com/mozilla/treeherder/commit/3ee87dbba69b26ae8216666bb385654d4b9809c0 Bug 1236592 - Heroku: Update django-pylibmc from v0.5.0 to v0.6.1 https://github.com/django-pylibmc/django-pylibmc/blob/master/CHANGELOG.rst https://github.com/django-pylibmc/django-pylibmc/compare/f8ae7aa8c134f81d3c391f2f49f9482b48f55d10...v0.6.1
Assignee | ||
Comment 3•8 years ago
|
||
I've just landed this as is, since it only affects Heroku and not stage/prod.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 4•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/b657b7bc6136e1afb99eaaec7b554d1260209d24 Bug 1236592 - Heroku: Update django-heroku-memcacheify from 0.8 to 1.0.0 https://github.com/rdegges/django-heroku-memcacheify/#changelog https://github.com/rdegges/django-heroku-memcacheify/compare/v0.8...v1.0.0
You need to log in
before you can comment on or make changes to this bug.
Description
•