posit-dev / posit-dev/positron
SSH-Remote Workspace Trust inconsistency
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
System details:
Positron and OS details:
Positron Version: 2025.04.0 (user setup) build 250
Code - OSS Version: 1.98.0
Commit: 627b3d723ee0b3a5bd86731a75902d419cafe22d
Date: 2025-04-03T16:50:39.209Z
Electron: 34.2.0
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Windows_NT x64 10.0.26100
Interpreter details:
N.A.
Describe the issue:
The listed items in the workspace trust view do not display the correct SSH remote. It seems to always indicate the last connected remote instead.
Steps to reproduce the issue:
- Connect to remote1, trust a folder
- Connect to remote2, trust a folder
- Check workspace trust view, both folders are listed as remote2
Expected or desired behavior:
Trusted folders should display the appropriate SSH remote
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing the two-remote sequence and inspecting the workspace trust view and its SSH remote data; done means each trusted folder displays the remote where it was trusted, rather than the most recently connected remote.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100