You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
include(closure://57f201094ffa4d4b72f510dfa76fe728): Failed to open stream: "Opis\Closure\ClosureStream::stream_open" call failed
{"exception":"[object] (ErrorException(code: 0): include(closure://57f201094ffa4d4b72f510dfa76fe728): Failed to open stream: \"Opis\\Closure\\ClosureStream::stream_open\" call failed at [...]\\vendor\\opis\\closure\\src\\ClosureStream.php:134)
My basic understanding of this library at version 4 is that, when something is serialized, it is serialized and the result+key is stored into a PHP runtime array cache, and when something needs to be unserialized, it will first find the result+key, and then look at said runtime array cache to give back the original thing. However, my use case is that the place to serialize the info and the place to unserialize them is different, and so the cache will always be empty, and so unserialization will always fail.
Is it possible for this library to just stop looking at the runtime array cache and just unserialize the information on demand?
The text was updated successfully, but these errors were encountered:
An example of such error:
To reproduce, see: Vectorial1024/laravel-process-async#13
My basic understanding of this library at version 4 is that, when something is serialized, it is serialized and the result+key is stored into a PHP runtime array cache, and when something needs to be unserialized, it will first find the result+key, and then look at said runtime array cache to give back the original thing. However, my use case is that the place to serialize the info and the place to unserialize them is different, and so the cache will always be empty, and so unserialization will always fail.
Is it possible for this library to just stop looking at the runtime array cache and just unserialize the information on demand?
The text was updated successfully, but these errors were encountered: