Skip to content

PHP Warning 'yii\base\ErrorException' with message 'Memcached::setMulti(): failed to set key nfsp-livef654ec3c4c849e91bf59178060603054' #450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ravirathoreds opened this issue Jan 22, 2020 · 1 comment
Closed

PHP Warning 'yii\base\ErrorException' with message 'Memcached::setMulti(): failed to set key nfsp-livef654ec3c4c849e91bf59178060603054' #450

ravirathoreds opened this issue Jan 22, 2020 · 1 comment

Comments

@ravirathoreds
Copy link

i am getting this issue .
PHP Version 7.2.26
memcached : 3.1.5

image

please help me to solve this issue.
@sodabrew
Copy link
Contributor

sodabrew commented Mar 1, 2020

I strongly advise a site like Stack Overflow for this question. I am closing it here.

@sodabrew sodabrew closed this as completed Mar 1, 2020
Krinkle added a commit to Krinkle/php-memcached that referenced this issue Aug 18, 2021
@Krinkle
Remove "failed to set key" warning from setMulti
97ee9f6 
This was introduced in 6837d89494,
pull php-memcached-dev#214. I suspect it
may have been a left-over from debugging something. The test was later
changed in 6837d89 to expect the warning in question, although other
similar tests don't encounter such warning currently.

It appears no other Memcached methods emit a PHP Warning when they encounter
a write read or failure. Instead, they typically turn their return value
into boolean false, and provide details via getResultMessage().

The introduction of this warning since php-memcached 3.0 has led to a number
of confused consumers (locally php-memcached-dev#260, php-memcached-dev#409, php-memcached-dev#450, and more reports
within downstream issue trackers).

Closes php-memcached-dev#409.
Krinkle added a commit to Krinkle/php-memcached that referenced this issue Aug 18, 2021
@Krinkle
Remove "failed to set key" warning from setMulti
2e2ba5f 
This was introduced in 6837d89494,
pull php-memcached-dev#214. I suspect it
may have been a left-over from debugging something. The test was later
changed in 6837d89 to expect the warning in question, although other
similar tests don't encounter such warning currently.

It appears no other Memcached methods emit a PHP Warning when they encounter
a write read or failure. Instead, they typically turn their return value
into boolean false, and provide details via getResultMessage().

The introduction of this warning since php-memcached 3.0 has led to a number
of confused consumers (locally php-memcached-dev#260, php-memcached-dev#409, php-memcached-dev#450, and more reports
within downstream issue trackers).

Closes php-memcached-dev#409.
Krinkle added a commit to Krinkle/php-memcached that referenced this issue Aug 18, 2021
@Krinkle
Remove "failed to set key" warning from setMulti
8642f43 
This was introduced in 6837d89494,
pull php-memcached-dev#214. I suspect it
may have been a left-over from debugging something. The test was later
changed in 6837d89 to expect the warning in question, although other
similar tests don't encounter such warning currently.

It appears no other Memcached methods emit a PHP Warning when they encounter
a write read or failure. Instead, they typically turn their return value
into boolean false, and provide details via getResultMessage().

The introduction of this warning since php-memcached 3.0 has led to a number
of confused consumers (locally php-memcached-dev#260, php-memcached-dev#409, php-memcached-dev#450, and more reports
within downstream issue trackers).

Closes php-memcached-dev#409.
@Krinkle Krinkle mentioned this issue Aug 18, 2021
Merged
Krinkle added a commit to Krinkle/php-memcached that referenced this issue Aug 18, 2021
@Krinkle
Remove "failed to set key" warning from setMulti
bf0fea3 
This was introduced in php-memcached-dev@6837d89494,
pull php-memcached-dev#214. I suspect it
may have been a left-over from debugging something. The test was later
changed in 6837d89 to expect the warning in question, although other
similar tests don't encounter such warning currently.

It appears no other Memcached methods emit a PHP Warning when they encounter
a write read or failure. Instead, they typically turn their return value
into boolean false, and provide details via getResultMessage().

The introduction of this warning since php-memcached 3.0 has led to a number
of confused consumers (locally php-memcached-dev#260, php-memcached-dev#409, php-memcached-dev#450, and more reports
within downstream issue trackers).

Closes php-memcached-dev#409.
sodabrew pushed a commit that referenced this issue Aug 23, 2021
@Krinkle
Remove "failed to set key" warning from setMulti (#490)
6d45715 
This was introduced in 6837d89494,
pull #214. I suspect it
may have been a left-over from debugging something. The test was later
changed in 6837d89 to expect the warning in question, although other
similar tests don't encounter such warning currently.

It appears no other Memcached methods emit a PHP Warning when they encounter
a write read or failure. Instead, they typically turn their return value
into boolean false, and provide details via getResultMessage().

The introduction of this warning since php-memcached 3.0 has led to a number
of confused consumers (locally #260, #409, #450, and more reports
within downstream issue trackers).

Closes #409.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sodabrew @ravirathoreds