Closed (fixed)
Project:
Memcache API and Integration
Version:
6.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2011 at 13:08 UTC
Updated:
15 May 2013 at 15:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
fgmSuggested patch fixes both issues, and make the stats return easier to debug by refactoring returns.
Comment #2
drewish commentedIt'd be best if we could avoid the warning rather than suppressing them.
Comment #3
drewish commentedThis and #1103796: memcache delete fix have some overlap. I'm a fan of #1103796 because it's a simpler patch.
Comment #4
fgmNeed to reroll to account for #1103796 now being committed. Reducing priority accordingly, since this was the most important part.
Comment #5
mikeytown2 commentedAnother issue for catching the warning if the memcache connection fails and reporting to watchdog.
#1011000: Catch & report errors thrown by $memcache->connect.
Comment #7
markpavlitski commentedMarking as fixed based on #1103796: memcache delete fix, #1103796: memcache delete fix and #1011000: Catch & report errors thrown by $memcache->connect. being committed and no activity in this issue for almost 2 years.
@fgm feel free to re-open if you're still experiencing the issue.