[Bug]: Open a local folder opens file picker for local instead of remote machine
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the GUI flow through “Open a local folder” and “empty project” with Polyscope on Windows and Polyscope-Server on Ubuntu through WSL. Trace the path.suggest and project.create_empty messages shown in the logs, then verify that remote folders are selectable and that project fields remain usable after an error.
Written by the indexing model from the issue text.
Description
Platform
Linux
Operating system version
Ubuntu 24.04.3 LTS (Through WSL)
System architecture
Windows
PolyScope Version
0.19.0 - Polyscope Server v0.17.0 (linux/x64)
Bug description
When trying to add a repository on a remote server (Polyscope running on Windows, Polyscope-server on Ubuntu through WSL) the open a local folder opens a file picker in Windows (which you cannot select the actual path on the machine). When selecting empty project and manually adding the path a error is shown:
Once that error is shown the fields (project name and folder) remains readonly/disabled and you need to restart to try again.
Steps to reproduce
- Run Polyscope on Windows/Mac device
- Run Polyscope-Server on linux device
- Try to add repository through GUI
- Click
Open a local folder-> local file picker is shown - Click empty project
- Fill in project name and folder (git repo) -> path gets autocompleted so that is working
- Press blue button
- Error message is shown
- Fields project name and path become readonly/disabled
Relevant log output
[ws] relay client: path.suggest {"type":"path.suggest","path":"/home/bkooij/test/"}
[ws] relay client: project.create_empty {"type":"project.create_empty","name":"test","directory":"/home/bkooij/test/"}
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from beyondcode/polyscope-community
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
beyondcode/polyscope-community#198 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
All issues in beyondcode/polyscope-community
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·