From 2cdf0866de7597ccfc8bffbe9dea0701cdb4bead Mon Sep 17 00:00:00 2001 From: KronosTheLate <61620837+KronosTheLate@users.noreply.github.com> Date: Wed, 14 Jun 2023 12:19:50 +0200 Subject: [PATCH 1/4] Create "troubleshooting.md" Add a bunch of potential error messages in "troubleshooting.md" --- "docs/src/\"troubleshooting.md\"" | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 "docs/src/\"troubleshooting.md\"" diff --git "a/docs/src/\"troubleshooting.md\"" "b/docs/src/\"troubleshooting.md\"" new file mode 100644 index 0000000..d41ed8d --- /dev/null +++ "b/docs/src/\"troubleshooting.md\"" @@ -0,0 +1,24 @@ +# Troubleshooting +This page will contain errors that have been seen before, and how they were fixed. The goal is that solutions to common problems are found here. +By "local REPL" a REPL running on the same computer as the host is meant. By "remote REPL", a REPL running on a different computer is meant. + +### IOError: connect: connection refused (ECONNREFUSED) +This error has been encountered when +1) Running `connect_repl()`, while attempting to connect to a local REPL. The problem was that no local REPL had previously run `serve_repl()`. To fix this, run `serve_repl()` in the local REPL. +2) Running `connect_remote()`, while attempting to connect to a local REPL. The problem was that no local REPL had previously run `serve_repl()`. To fix this, run `serve_repl()` in the local REPL. +3) Running `connect_remote()`, while attempting to connect to a remote REPL. The problem was that no address was provided. To fix this, pass an adress as a string to `connect_remote`, as in `connect_remote("pi@192.168.4.2")` + +### RemoteREPL stream was closed while reading header +This error has been encountered when +1) Running `connect_remote("pi@192.168.4.2")`, while attempting to connect to a remote REPL. The problem was that the remote REPL had not previously run `serve_repl()`. To fix this, run `serve_repl()` in the remote REPL. +2) Running `connect_repl("pi@192.168.4.2")`, while attempting to connect to a remote REPL. The problem was that the remote REPL had not previously run `serve_repl()`. To fix this, run `serve_repl()` in the remote REPL. + +### Bad owner or permissions on /home/username/.ssh/config +This error is raised by [this](https://github.com/openssh/openssh-portable/blob/947a3e829a5b8832a4768fd764283709a4ca7955/readconf.c#L1711) line of code, from OpenSSH. +The requirements translates to that "the config file must be owned by root or by the user running the ssh and can not be writable by any group or other users." +(Quoted from [this](https://superuser.com/questions/1212402/bad-owner-or-permissions-on-ssh-config-file) thread). The fix is therefore to remove write premissions for +any group or other users. On a linux system, this is acomplished by running the following code. +``` +chmod go-w /home/username/.ssh/config +``` +If you are using a different operating system, please google how to remove write premissions on files, and try to do the same thing. From 8bd1d44cafea47fff3897ba88c2224fb2bad3af4 Mon Sep 17 00:00:00 2001 From: KronosTheLate Date: Tue, 24 Oct 2023 16:24:05 +0200 Subject: [PATCH 2/4] Disable nagles algorithm --- src/client.jl | 1 + 1 file changed, 1 insertion(+) diff --git a/src/client.jl b/src/client.jl index 4c28b2e..90ab30d 100644 --- a/src/client.jl +++ b/src/client.jl @@ -139,6 +139,7 @@ function setup_connection!(conn::Connection) tunnel=conn.tunnel, ssh_opts=conn.ssh_opts, region=conn.region, namespace=conn.namespace) end + Sockets.nagle(socket, false) # Disables nagles algorithm. Appropriate for interactive connections. try verify_header(socket) catch exc From 9cb86a1ee38ad8aa377df183b39822911708aa0b Mon Sep 17 00:00:00 2001 From: Claire Foster Date: Tue, 16 Jul 2024 01:58:29 +0200 Subject: [PATCH 3/4] Move troubleshooting into howto.md This ensures it's in a standard section of the docs and will be built with the rest of the docs. --- "docs/src/\"troubleshooting.md\"" | 24 ------------------------ docs/src/howto.md | 26 ++++++++++++++++++++++++++ 2 files changed, 26 insertions(+), 24 deletions(-) delete mode 100644 "docs/src/\"troubleshooting.md\"" diff --git "a/docs/src/\"troubleshooting.md\"" "b/docs/src/\"troubleshooting.md\"" deleted file mode 100644 index d41ed8d..0000000 --- "a/docs/src/\"troubleshooting.md\"" +++ /dev/null @@ -1,24 +0,0 @@ -# Troubleshooting -This page will contain errors that have been seen before, and how they were fixed. The goal is that solutions to common problems are found here. -By "local REPL" a REPL running on the same computer as the host is meant. By "remote REPL", a REPL running on a different computer is meant. - -### IOError: connect: connection refused (ECONNREFUSED) -This error has been encountered when -1) Running `connect_repl()`, while attempting to connect to a local REPL. The problem was that no local REPL had previously run `serve_repl()`. To fix this, run `serve_repl()` in the local REPL. -2) Running `connect_remote()`, while attempting to connect to a local REPL. The problem was that no local REPL had previously run `serve_repl()`. To fix this, run `serve_repl()` in the local REPL. -3) Running `connect_remote()`, while attempting to connect to a remote REPL. The problem was that no address was provided. To fix this, pass an adress as a string to `connect_remote`, as in `connect_remote("pi@192.168.4.2")` - -### RemoteREPL stream was closed while reading header -This error has been encountered when -1) Running `connect_remote("pi@192.168.4.2")`, while attempting to connect to a remote REPL. The problem was that the remote REPL had not previously run `serve_repl()`. To fix this, run `serve_repl()` in the remote REPL. -2) Running `connect_repl("pi@192.168.4.2")`, while attempting to connect to a remote REPL. The problem was that the remote REPL had not previously run `serve_repl()`. To fix this, run `serve_repl()` in the remote REPL. - -### Bad owner or permissions on /home/username/.ssh/config -This error is raised by [this](https://github.com/openssh/openssh-portable/blob/947a3e829a5b8832a4768fd764283709a4ca7955/readconf.c#L1711) line of code, from OpenSSH. -The requirements translates to that "the config file must be owned by root or by the user running the ssh and can not be writable by any group or other users." -(Quoted from [this](https://superuser.com/questions/1212402/bad-owner-or-permissions-on-ssh-config-file) thread). The fix is therefore to remove write premissions for -any group or other users. On a linux system, this is acomplished by running the following code. -``` -chmod go-w /home/username/.ssh/config -``` -If you are using a different operating system, please google how to remove write premissions on files, and try to do the same thing. diff --git a/docs/src/howto.md b/docs/src/howto.md index 66878f1..ec6e727 100644 --- a/docs/src/howto.md +++ b/docs/src/howto.md @@ -127,3 +127,29 @@ In environments without any REPL integrations like Jupyter or Pluto notebooks yo connect_remote(); ``` which will allow you to use `@remote` without the REPL mode. + +## Troubleshooting + +This section contains errors that have been seen before, and how they were fixed. The goal is that solutions to common problems are found here. +By "local REPL" a REPL running on the same computer as the host is meant. By "remote REPL", a REPL running on a different computer is meant. + +### IOError: connect: connection refused (ECONNREFUSED) +This error has been encountered when +1) Running `connect_repl()`, while attempting to connect to a local REPL. The problem was that no local REPL had previously run `serve_repl()`. To fix this, run `serve_repl()` in the local REPL. +2) Running `connect_remote()`, while attempting to connect to a local REPL. The problem was that no local REPL had previously run `serve_repl()`. To fix this, run `serve_repl()` in the local REPL. +3) Running `connect_remote()`, while attempting to connect to a remote REPL. The problem was that no address was provided. To fix this, pass an adress as a string to `connect_remote`, as in `connect_remote("pi@192.168.4.2")` + +### RemoteREPL stream was closed while reading header +This error has been encountered when +1) Running `connect_remote("pi@192.168.4.2")`, while attempting to connect to a remote REPL. The problem was that the remote REPL had not previously run `serve_repl()`. To fix this, run `serve_repl()` in the remote REPL. +2) Running `connect_repl("pi@192.168.4.2")`, while attempting to connect to a remote REPL. The problem was that the remote REPL had not previously run `serve_repl()`. To fix this, run `serve_repl()` in the remote REPL. + +### Bad owner or permissions on /home/username/.ssh/config +This error is raised by [this](https://github.com/openssh/openssh-portable/blob/947a3e829a5b8832a4768fd764283709a4ca7955/readconf.c#L1711) line of code, from OpenSSH. +The requirements translates to that "the config file must be owned by root or by the user running the ssh and can not be writable by any group or other users." +(Quoted from [this](https://superuser.com/questions/1212402/bad-owner-or-permissions-on-ssh-config-file) thread). The fix is therefore to remove write premissions for +any group or other users. On a linux system, this is acomplished by running the following code. +``` +chmod go-w /home/username/.ssh/config +``` +If you are using a different operating system, please google how to remove write premissions on files, and try to do the same thing. From 12c38d9d001f4514b9b8065e26ddc610534c4a1f Mon Sep 17 00:00:00 2001 From: Claire Foster Date: Tue, 16 Jul 2024 02:08:12 +0200 Subject: [PATCH 4/4] Set min test version to julia-1.6 --- .github/workflows/CI.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/CI.yml b/.github/workflows/CI.yml index 0cedb9c..6c943c9 100644 --- a/.github/workflows/CI.yml +++ b/.github/workflows/CI.yml @@ -13,7 +13,7 @@ jobs: fail-fast: false matrix: version: - - '1.5' + - '1.6' - '1' - 'nightly' os: