Last modified: 2011-03-13 18:06:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 2347 - Add defensive code for failure of Turck cache puts.
Add defensive code for failure of Turck cache puts.
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.4.x
All All
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-07 23:45 UTC by Carlton Brown
Modified: 2011-03-13 18:06 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Carlton Brown 2005-06-07 23:45:51 UTC
The wrapper class for MW, BagOTurckStuff, does not check the return 
value of mmcache_put.  Thus, functions that depend on this caching 
are unaware that caching has failed, and unexplained failures 
result.

Suggestions:
1) Check the return value of mmcache_put and possibly mmcache_get, 
to handle or log exceptional cases

2) Add warning comment in LocalSettings.php that Turck data caching 
is not certified for all environments and may cause message 
substitution failures
Comment 1 Carlton Brown 2005-06-07 23:47:13 UTC
First 2 phrases should have read: "The MW wrapper class for Turck Mmemcache, 
BagOTurckStuff"
Comment 2 Brion Vibber 2005-12-12 02:41:34 UTC
The caches are assumed to be lossy, so a silent failure is not a problem.
Resolving WONTFIX.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links