lapce / lapce/lapce

Remote Development Icon going red and not showing any error I could use to figure out what is wrong

Open
#1,109 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-remote C-bug
Dominant language
Rust
Stars
38.9k
Forks
1.3k
Avg merge
19m
Merged PRs (30d)
1

Description

Lapce Version

0.2.0

System information

I am trying to connect from a macOS 12.5.1 (21G83) Early 2015 Air to a server running illumos current and another one running ArchLinux current amd64

Describe the bug

I try to connect to an SSH host and type in the name as I have it configured in my ~/.ssh/config oibuild, Lapce tries to connect but fails and then show a red connection icon.
For ssh I use the command ssh oibuild and this config.

Host oibuild
  User *****
  Hostname build
  ProxyJump ****@$PUBLIC_IP
  ForwardAgent yes
  AddressFamily inet
  TCPKeepAlive=yes
  ServerAliveCountMax=20
  ServerAliveInterval=60

I assume something with the ssh command fails but I can't figure out what as I can't find the log and no documentation on how to create one. I am a rust developer and illumos Contributor so if I need to compile pace from source I am happy to do that to get logs but I would like some mentoring to fix this bug at least.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the connection with the reported ~/.ssh/config entry and the ssh oibuild command, then trace how Lapce reports a failed remote connection. Done means the red connection state provides an actionable error or points to logs that explain the SSH failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
devtools, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.