Repeated error message when change detection is enabled

[benjamineskola]

Describe the bug

Every few seconds from startup I get the following error message:

Error executing luv callback:
vim/_editor.lua:0: E5560: nvim_echo must not be called in a lua loop callback
stack traceback:
        [C]: in function 'nvim_echo'
        vim/_editor.lua: in function 'notify'
        ...s/ben/Library/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:198: in function 'notify'
        ...s/ben/Library/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:222: in function 'warn'
        ...Library/nvim/lazy/lazy.nvim/lua/lazy/manage/reloader.lua:68: in function <...Library/nvim/lazy/lazy.nvim/lua/lazy/manage/reloader.lua:35>

Which version of Neovim are you using?

NVIM v0.8.1
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by [email protected]

Features: +acl +iconv +tui
See ":help feature-compile"

To Reproduce
Make sure to read https://github.com/folke/lazy.nvim/wiki/Minimal-%60init.lua%60-to-Reproduce-an-Issue

Steps to reproduce the behavior:

This occurs with a neovim config that I modelled after the one linked in the readme (folke/dot). It is resolved by setting change_detection = { enabled = false }`, but obviously that is not ideal. My init.lua, lazy.lua, plugins.lua.

I will follow up with disabling plugins and enabling one by one to determine whether a specific plugin creates the issue.

[folke]

Fixed!

This was actually caused by lazy trying to show you a warning that you need to set mapleader BEFORE loading lazy. Otherwise your keymaps might break

[benjamineskola]

Thanks for such a quick fix! Lazy.nvim seems great so far. :)