SCP'ing Config To Remote Fails

Question

SCP'ing Config To Remote Fails

Opened this issue 7 months ago · 12 comments

It appears that I am unable to copy my nvim config to the remote host, and I cannot figure out why this is happening. I have tried completely deleting my whole setup including cache and reinstalling.

Answer 1 · 2024-06-19T05:15:04.000Z

Sorry about this. This might have been caused by the latest release. Can you downgrade to ~~v0.2.9~~ v0.3.9 and let me know. I think that should make it work. For me to handle this edge case, could you provide the output your SSH version info (ssh -V).

Edit: Version -> v0.3.9 not v0.2.9

Answer 2 · 2024-06-19T13:10:16.000Z

I am having the same problem here. I tried manually change the configuration path my plugin config.lua file as shown in the documentation (see code below), but did not work.

return {
    "amitds1997/remote-nvim.nvim",
    version = "*",                 -- Pin to GitHub releases
    dependencies = {
        "nvim-lua/plenary.nvim",   -- For standard functions
        "MunifTanjim/nui.nvim",    -- To build the plugin UI
        "nvim-telescope/telescope.nvim", -- For picking b/w different remote methods
    },
    config = function()
        require("remote-nvim").setup({
            -- Remote configuration
            remote = {
                app_name = "nvim", -- This directly maps to the value NVIM_APPNAME. If you use any other paths for configuration, also make sure to set this.
                -- List of directories that should be copied over
                copy_dirs = {
                    -- What to copy to remote's Neovim config directory
                    config = {
                        base = "~/.dotfiles/.config/nvim/",
                        dirs = "*", -- Directories that should be copied over. "*" means all directories. To specify a subset, use a list like {"lazy", "mason"} where "lazy", "mason" are subdirectories}
                    }
                }
            }
        })
    end
}

Downgrading to v0.2.7 has worked, since v0.2.9 is not available in the release tags.
Any idea of the cause of the issue?

Answer 3 · 2024-06-19T14:29:25.000Z

Yeah, I do know the cause. Basically, when copying all dirs we use the syntax <base-path>/. to indicate the directory path <base-path> (in the latest release). This seems to not work on some systems. So, we see the error: no such filename . It somehow interprets . as a filename and not the denotion for current directory.

So, having the SSH client and system information would help me debug this.

Answer 4 · 2024-06-19T14:32:53.000Z

Downgrading to v0.2.7 has worked, since v0.2.9 is not available in the release tags.
Any idea of the cause of the issue?

Sorry, the version would be v0.3.9 (previous to the latest release)

Answer 5 · 2024-06-19T15:01:31.000Z

Here are a few informations regarding the SSH and my system:

OpenSSH_8.9p1 Ubuntu-3ubuntu0.7, OpenSSL 3.0.2 15 Mar 2022
Ubuntu 22.04.4 LTS
zsh 5.8.1 (x86_64-ubuntu-linux-gnu)

Answer 6 · 2024-06-19T19:09:58.000Z

Here is my ssh version:

OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021

NAME="Rocky Linux"
VERSION="8.10 (Green Obsidian)"

Answer 7 · 2024-07-06T05:17:37.000Z

Hey all, got busy so never got around to this. Just for some context, this is the solution that I tried to implement (in the latest release) and it worked on some systems but not all. I'm digging more into it and would let you both know once a fix/solution is released.

One other thing I noticed is that, you both have OpenSSH 8.x versions, mine is OpenSSH 9.x. So, maybe it might have been patched back in the 9.x releases.

Answer 8 · 2024-07-10T15:15:19.000Z

I can confirm that I have the same problem when communicating between two docker containers using OpenSSH_8.2

@amitds1997 Is there any way to log the raw ssh/scp commands that are being run at each step? setting log.level = "debug" only adds a little more information.

Answer 9 · 2024-07-10T15:31:37.000Z

I can confirm that I have the same problem when communicating between two docker containers using OpenSSH_8.2

@amitds1997 Is there any way to log the raw ssh/scp commands that are being run at each step? setting log.level = "debug" only adds a little more information.

Thanks for your feedback. I will make sure to add more verbose logging for the ssh/scp command.

Meanwhile, I do have a fix that I'm testing out. Hope the workaround mentioned above works for you right now.

Answer 10 · 2024-07-10T16:40:18.000Z

I can confirm that upgrading to OpenSSH_9.8 solves this issue! Just as a sanity check, it is expected that a RemoteStart from within a nvim -u repro.lua client will have an empty vimrc/lua configuration correct?

I came across the above problem while trying to debug my main machine which fails on the echo 'Hello' check with the following output:

DEBUG Wed 10 Jul 2024 13:19:24 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:866: [ssh][ubuntu-container] Starting remote neovim launch
DEBUG Wed 10 Jul 2024 13:19:24 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:141: Did not find any existing configuration. Creating one now..
DEBUG Wed 10 Jul 2024 13:19:24 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:995: ["ssh"]["ubuntu-container"] Running "echo 'Hello'"
DEBUG Wed 10 Jul 2024 13:19:25 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:1015: ["ssh"]["ubuntu-container"] Running "echo 'Hello'" completed
ERROR Wed 10 Jul 2024 13:19:25 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:973: 'Testing remote connection' failed.
stack traceback:
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:974: in function '_handle_job_completion'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:1017: in function 'run_command'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:142: in function '_setup_workspace_variables'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:872: in function '_launch_neovim'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:883: in function <.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:882>
	[C]: in function 'xpcall'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:759: in function <.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:758> 

FAILED JOB OUTPUT (SO FAR)
bash: -c: line 1: unexpected EOF while looking for matching `''
bash: -c: line 2: syntax error: unexpected end of file

Which uses OpenSSH_9.8, but since I am going from a NixOS machine to a docker container, there are more than a few moving parts to investigate along the lines of #150 before I feel comfortable opening a new issue. If you have any ideas what might be causing this please let me know!

Thank you for this amazing plugin, I think it has great potential :)

Answer 11 · 2024-07-12T06:19:11.000Z

I can confirm that upgrading to OpenSSH_9.8 solves this issue!

Thanks for doing this 👍 This helps!

Just as a sanity check, it is expected that a RemoteStart from within a nvim -u repro.lua client will have an empty vimrc/lua configuration correct?

Yup, the hope is this will help isolate issues that are caused by the plugin and not by the user configuration. And give me an easy way to reproduce most issues. You can add your plugins and configuration specific to your setup in it and add it to the issue so that I can reproduce it too.

I came across the above problem while trying to debug my main machine which fails on the echo 'Hello' check with the following output:

DEBUG Wed 10 Jul 2024 13:19:24 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:866: [ssh][ubuntu-container] Starting remote neovim launch
DEBUG Wed 10 Jul 2024 13:19:24 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:141: Did not find any existing configuration. Creating one now..
DEBUG Wed 10 Jul 2024 13:19:24 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:995: ["ssh"]["ubuntu-container"] Running "echo 'Hello'"
DEBUG Wed 10 Jul 2024 13:19:25 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:1015: ["ssh"]["ubuntu-container"] Running "echo 'Hello'" completed
ERROR Wed 10 Jul 2024 13:19:25 BST /nix/store/8qvna5qxr8yil5l53lchi9db9r7frfb7-vim-pack-dir/pack/myNeovimPackages/start/remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:973: 'Testing remote connection' failed.
stack traceback:
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:974: in function '_handle_job_completion'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:1017: in function 'run_command'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:142: in function '_setup_workspace_variables'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:872: in function '_launch_neovim'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:883: in function <.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:882>
	[C]: in function 'xpcall'
	.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:759: in function <.../remote-nvim.nvim/lua/remote-nvim/providers/provider.lua:758> 

FAILED JOB OUTPUT (SO FAR)
bash: -c: line 1: unexpected EOF while looking for matching `''
bash: -c: line 2: syntax error: unexpected end of file

Which uses OpenSSH_9.8, but since I am going from a NixOS machine to a docker container, there are more than a few moving parts to investigate along the lines of #150 before I feel comfortable opening a new issue. If you have any ideas what might be causing this please let me know!

I have created a new issue to track this: #157. Let's tackle it there!

Thank you for this amazing plugin, I think it has great potential :)

Thanks, I appreciate it! ❤️

Answer 12 · 2024-10-10T08:47:37.000Z

Hi there, are there still plans to get this working with OpenSSH 8.X?