Created attachment 450704 [details]
Patch to clear the compression flag for integer, float, and boolean data
Description of problem:
php-pecl-memcache has a bug preventing the successful storage of integer, float,
or boolean values in memcached.
Version-Release number of selected component (if applicable):
Always when storing and retrieving integer, float, or boolean values, with compression enabled.
Steps to Reproduce:
Example scripts that reproduce the bug can be found in upstreams bug tracker at:
Retrieving a stored value fails, the stored value is lost, and PHP logs a message with level NOTICE:
MemcachePool::get(): Failed to uncompress data
Retrieving a stored value should succeed and return the stored value.
The upstream author changed php-pecl-memcache so that compression is never used to store values of integer, float, and boolean types, but forgot to clear the compression flag in case it should be set. Because of this, values that were stored this way fail decompression on retrieval, because they are not compressed in the first place.
The attached patch fixes the issue.
Upstream has released version 3.0.5 which contains the fix from the patch attached to this Bugzilla entry. Please upgrade to the latest version.
Thanks for reporting this.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Had to clear Rebase keyword to keep bot from resetting relnote flag - there is a relnote for this rebase, it is just attached to another bug fixed by the rebase
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.