Closed somini closed 4 years ago
From https://pypi.org/project/msgpack/#description and msgpack/msgpack-python@5534d0c#diff-88b99bb28683bd5b7e3a204826ead112R40, I'm guessing the Unpacker needs the raw_as_bytes option to keep the same behaviour as before?
You can change the pynvim's msgpack argument and test it to fix. pip supports install from git repository. So you should create the PR instead. Because you can reproduce the problem easily.
https://github.com/neovim/pynvim/issues/299#issuecomment-362790688
It may be related issue.
deoplete uses unicode_errors='surrogateescape'
for it.
https://github.com/neovim/pynvim/blob/3efa4878464021f2c23b311f43a599318595177d/pynvim/compat.py#L34
Python3 unicode_errors_default
is surrogateescape
.
Why it is error??
OH....
https://github.com/neovim/pynvim/blob/master/pynvim/msgpack_rpc/msgpack_stream.py#L24
It is broken.
It must be:
self._unpacker = Unpacker(unicode_errors=unicode_errors_default)
@bfredl Ping.
I think my issue(https://github.com/neovim/pynvim/issues/435) is related to this. That bug is reproduced only on msgpack 1.0.0.
@somini @tomtomjhj Please test #439.
@Shougo That works for me. Thanks!
@somini @tomtomjhj Please test #439.
@Shougo Can confirm #439 fixes this, thanks for the quick turn around.
OK.
@bfredl Can you merge the PR?
What's the status of this?
@bfredl seems no activity now... https://github.com/bfredl
Ping @neovim
This has emailed 21 people. I'm sorry...
Fixed now.
I apologise, but this has been fixed and merged to master
, but no new release has been done. Meaning this hasn't hit the repositories yet.
https://github.com/neovim/pynvim/compare/0.4.1...master
Since this is a breaking change, I believe a new release is in order.
@justinmk Can you release the new version?
If i recall, @bfredl is the only one w/ pip permissions. I think that was the hold up (but I don't remember for sure)
Oh..
release steps are here: https://github.com/neovim/pynvim#release
Let's see if @bfredl replies, else I will think about what to do in a few days
Bump...
Just in case we're stuck for a bit you can pip install from a git revision. That might solve the problem for you.
Friendly bump. Personally I'm not stuck, I'm sticking with the old version.
@bfredl is still AWOL, I hope everything is all right.
Friendly bump. There's still no release on pip that includes this fix, which means distros don't pickup the new release.
Hm...
Another friendly bump. This is still broken.
Thanks for the ping. I've released a new version of pynvim.
Thanks, can confirm this is now hit the Arch Linux repos:
$ pacman -Q python-{msgpack,pynvim}
python-msgpack 1.0.0-1
python-pynvim 0.4.2-1
This hanged nvim completely on hitting backspace in a denite buffer (I'm on the old Shougo/denite.nvim@67475c7, before the v3 rewrite).
Here's a traceback:
I have the latest v0.4.1 on the latest Arch Linux:
Downgrading to
python-msgpack
v0.6.2 resolves it.See #436
From https://pypi.org/project/msgpack/#description and https://github.com/msgpack/msgpack-python/commit/5534d0c7af0114db3d27f7b96c82a7fe22ce1e40#diff-88b99bb28683bd5b7e3a204826ead112R40, I'm guessing the Unpacker needs the
raw_as_bytes
option to keep the same behaviour as before?