This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 53
Fatal error storing objects in xcache adapter #58
Comments
Oh lordy, looks like namespaces are broken too:
|
Closed
Ohhh it looks like they removed the serializing support and they have problems keeping the extension up-to-date. (Could be because of less of interest as with opcache and apcu exists a much more common approach) Can you add a PR as hotfix and I will think about how to make the tests run in travis. In my opinion we could also think about deprecating this adapter. |
WTF Why is that a fatal error :( |
Got me there ;) Is #59 OK or would you rather I did a new hotfix/58 PR with just the fixes for storing objects and namespaces? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As the docs say:
Looks the adapter needs to have "object" => false in it's supportedDatatypes options and also throw an exception instead of fatal error. I'm using xcache 3.2.0.
BTW, xcache > 3.1.0 does support CLI, so there's no need to skip the tests for stuff like this. I'll do a PR.
The text was updated successfully, but these errors were encountered: