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
NVIM v0.8.3
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compiled by runneradmin@fv-az171-224
Features: -acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM\sysinit.vim"
fall-back for $VIM: "C:/Program Files (x86)/nvim/share/nvim"
Run :checkhealth for more info
git --version: git version 2.24.1.windows.2
Operating system/version: W10
Terminal name/version: Neovide
Steps to reproduce
Add use 'nvim-treesitter/treesitter' to plugins.lua
Restart Neovim
Use :PackerSync
Get the following error for treesitter: fatal: could not read Username for 'https://github.com': terminal prompts disabled
Follow thesetutorials to generate an SSH key and put it in GitHub, then type git config --global url.ssh://git@github.com/.insteadOf https://github.com/ into Git Bash (So basically, follow terminal prompts disabled #748)
Restart Neovim
Use :PackerSync
Actual behaviour
Got the following error for all plugins:
Cloning into 'C:\Users\mikwee\AppData\Local\nvim-data\site\pack\packer\start\[NAME OF PACKAGE]'...
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Expected behaviour
I expect Packer to install all specified packages correctly.
packer files
Plugin specification file(s)
You mean plugins.lua? Here it is:
localensure_packer=function()
localfn=vim.fnlocalinstall_path=fn.stdpath('data')..'/site/pack/packer/start/packer.nvim'iffn.empty(fn.glob(install_path)) >0thenfn.system({'git', 'clone', '--depth', '1', 'https://github.com/wbthomason/packer.nvim', install_path})
vim.cmd[[packadd packer.nvim]]returntrueendreturnfalseendlocalpacker_bootstrap=ensure_packer()
returnrequire('packer').startup(function(use)
use'wbthomason/packer.nvim'use'ellisonleao/gruvbox.nvim'use'nvim-tree/nvim-tree.lua'use'nvim-tree/nvim-web-devicons'use'nvim-lualine/lualine.nvim'use'nvim-treesitter/treesitter'use {
'nvim-telescope/telescope.nvim',
tag='0.1.0',
requires= { {'nvim-lua/plenary.nvim'} }
}
-- Automatically set up your configuration after cloning packer.nvim-- Put this at the end after all pluginsifpacker_bootstrapthenrequire('packer').sync()
endend)
packer log file
[WARN 18/02/2023 00:05:38 38006809283100] ...ite\pack\packer\start\packer.nvim/lua/packer/display.lua:812: No plugin selected!
[WARN 18/02/2023 00:05:58 38026952738000] ...ite\pack\packer\start\packer.nvim/lua/packer/display.lua:711: No plugin selected!
[WARN 18/02/2023 00:06:06 38034808999600] ...ite\pack\packer\start\packer.nvim/lua/packer/display.lua:711: No plugin selected!
[WARN 18/02/2023 00:06:06 38035241346200] ...ite\pack\packer\start\packer.nvim/lua/packer/display.lua:711: No plugin selected!
[WARN 18/02/2023 00:39:22 40031658395200] ...ite\pack\packer\start\packer.nvim/lua/packer/display.lua:730: Unable to find the diff for this line
Host key verification failed is an ssh issue, not a packer issue. You can verify this by trying to git clone the package yourself.
This happens when the fingerprint of the host changes.
This must not happen for github. This usually means someone's doing an MITM attack.
I don't know how to debug this on windows. On Linux the host keys are stored in ~/.ssh/known_hosts.
The first time you connect to a host, it's key gets stored here. If someone tries to MITM you, ssh will be able to detect this and it will say that the key is different from the one that we first encountered.
nvim --version
:git --version
:git version 2.24.1.windows.2
Steps to reproduce
use 'nvim-treesitter/treesitter'
toplugins.lua
:PackerSync
fatal: could not read Username for 'https://github.com': terminal prompts disabled
git config --global url.ssh://git@github.com/.insteadOf https://github.com/
into Git Bash (So basically, follow terminal prompts disabled #748):PackerSync
Actual behaviour
Got the following error for all plugins:
Expected behaviour
I expect Packer to install all specified packages correctly.
packer files
Plugin specification file(s)
You mean
plugins.lua
? Here it is:packer log file
packer compiled file
packer_compiled.lua
for me, but here it goes:The text was updated successfully, but these errors were encountered: