Skip to content
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.

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

neovim-qt with Nvim v0.11.0 shows many "no notification handler registered" warnings #29363

Open
eyalk11 opened this issue Jun 15, 2024 · 4 comments
Labels
api libnvim, Nvim RPC API events events, autocommands rpc status:blocked-external Needs a third-party / external change or fix
Milestone

Comments

@eyalk11
Copy link
Contributor

eyalk11 commented Jun 15, 2024

Problem

Those come every two seconds from the moment I open nvim . It comes in two flavors Dir and Gui errors.

Everything (i.e. the same profile) works well in nvim 0.10 .


01:28:04 msg_show Error detected while processing VimEnter Autocommands for "*"..function LoadBaseInserts[35]..provider#python3#Call:
01:28:04 msg_show line    1:
01:28:04 msg_show E5108: Error executing lua Vim:no notification handler registered for "Dir"
stack traceback:
	[C]: at 0x7ff7ea9d6840
   Error  01:28:04 msg_show.emsg no notification handler registered for "Gui"
Run ":verbose version" for more info
01:28:20 msg_show   NoiceHistory "[Scratch]" 11 lines --9%--
   Error  01:28:20 msg_show.emsg   NoiceHistory no notification handler registered for "Dir"
01:28:20 msg_show   NoiceHistory no notification handler registered for "Dir"
01:28:20 msg_show   NoiceHistory no notification handler registered for "Gui"
01:28:20 msg_show "[Scratch]" 11 lines --9%--
   Error  01:28:21 msg_show.emsg no notification handler registered for "Gui"
01:28:21 msg_show "[Scratch]" 11 lines --18%--
   Error  01:28:21 msg_show.emsg no notification handler registered for "Gui"


It is really not debugable this way. 


01:28:06 msg_show   version NVIM v0.11.0-dev-250+g61aabe073
01:28:06 msg_show   version Build type: RelWithDebInfo
01:28:06 msg_show   version LuaJIT 2.1.1716656478

Steps to reproduce

my neovim profile

Expected behavior

Works

Neovim version (nvim -v)

NVIM v0.11.0-dev-250+g61aabe073

Vim (not Nvim) behaves the same?

no idea

Operating system/version

Windows

Terminal name/version

nvim-qt

$TERM environment variable

unk

Installation

nightly

@eyalk11 eyalk11 added the bug issues reporting wrong behavior label Jun 15, 2024
@eyalk11
Copy link
Contributor Author

eyalk11 commented Jun 15, 2024

#8053
I tried UpdateRemotePlugins

@eyalk11 eyalk11 changed the title After updating to neovim v.11.0 , got a lot of notification handler errors After updating to neovim v0.11.0 , got a lot of notification handler errors Jun 15, 2024
@eyalk11
Copy link
Contributor Author

eyalk11 commented Jun 15, 2024

After removing neovim-gui-shim it seems to be solved.

@zeertzjq zeertzjq added the needs:repro We need minimal steps to reproduce the issue label Jun 15, 2024
@doctorcolossus
Copy link

doctorcolossus commented Jun 17, 2024

I have also been getting this behavior since upgrading to nvim 0.11 with ppa:neovim-ppa/unstable.

For me, this is triggered by Shougo/deoplete.nvim and has prevented its usage since upgrading nvim.

no notification handler registered for "Dir"
no notification handler registered for "Gui"
no notification handler registered for "Gui"
no notification handler registered for "Gui"

on startup if g:deoplete#enable_at_startup = 1, and then no notification handler registered for "Gui" after each keystroke in insert mode with deoplete enabled.

I experience this issue with the following exact package pairs from the aforementioned PPA:

Despite the package names above containing the text "0.10.0", they do actually provide nvim 0.11.

Uninstalling, removing the PPA, and downgrading to 0.10 with the deb file provided here resolves the regression for me. Thanks to @eyalk11 for pointing out that nvim 0.11 is the problem. I had spent months without my deoplete autocompletion and a lot of time trying to figure out what had been wrong with it, so happy to have it working again now and hope this can be fixed in subsequent neovim versions.

@justinmk justinmk changed the title After updating to neovim v0.11.0 , got a lot of notification handler errors neovim-qt with Nvim v0.11.0 shows many notification handler errors Jun 17, 2024
@justinmk justinmk added status:blocked-external Needs a third-party / external change or fix api libnvim, Nvim RPC API rpc events events, autocommands and removed bug issues reporting wrong behavior needs:repro We need minimal steps to reproduce the issue labels Jun 17, 2024
@justinmk
Copy link
Member

This is because something is broadcasting an event via rpcnotify(0, ...) and neovim-qt is showing this warning. equalsraf/neovim-qt#1112

Nvim-qt should just not show that warning.

For reference, this was indirectly caused by #28487 . I expected some issues like this, but so far only nvim-qt seems to be doing this kind of thing (complaining when it sees an unknown event). So I'm hoping that nvim-qt will change its behavior to quietly ignore unknown events.

@justinmk justinmk added this to the unplanned milestone Jun 17, 2024
@justinmk justinmk changed the title neovim-qt with Nvim v0.11.0 shows many notification handler errors neovim-qt with Nvim v0.11.0 shows many "no notification handler registered" warnings Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api libnvim, Nvim RPC API events events, autocommands rpc status:blocked-external Needs a third-party / external change or fix
Projects
None yet
Development

No branches or pull requests

4 participants