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
If a key in a table is nil, the unpack will report an error. But it seems possible to create such an array in msgpack so maybe the Lua unpacker should just ignore it since it cannot be used this way.
Initially for me, the problems comes from the PHP msgpack extension that doesn't serialize sessions correctly and adds a nil indexed key in the array. I was trying to use redis as a session store to share sessions between Openresty (Lua) and PHP (I could do the same with Nodejs for example). The PHP unpack just ignores the nil indexed key/value. See the following issue for some details about the problem. msgpack/msgpack-php#50
If a key in a table is nil, the unpack will report an error. But it seems possible to create such an array in msgpack so maybe the Lua unpacker should just ignore it since it cannot be used this way.
Initially for me, the problems comes from the PHP msgpack extension that doesn't serialize sessions correctly and adds a nil indexed key in the array. I was trying to use redis as a session store to share sessions between Openresty (Lua) and PHP (I could do the same with Nodejs for example). The PHP unpack just ignores the nil indexed key/value. See the following issue for some details about the problem.
msgpack/msgpack-php#50
There is the same issue in the Lua MessagePack implementation as described here:
https://github.com/fperrad/lua-MessagePack/issues/14
The text was updated successfully, but these errors were encountered: