Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Folders randomly close when working in Go submodule, added as separate top-level folder #121217

Closed
distinctdan opened this issue Apr 13, 2021 · 7 comments
Assignees
Labels
file-explorer Explorer widget issues info-needed Issue requires more information from poster *out-of-scope Posted issue is not in scope of VS Code

Comments

@distinctdan
Copy link

distinctdan commented Apr 13, 2021

Issue Type: Bug

I have a Go project that has the following structure:

project
    <some files>
    subfolder
        <more files>
        go.mod
    go.mod
subfolder

VSCode recommends that I add the subfolder as a separate workspace folder in order for go autocomplete and error highlighting to work. However, when I do that, vscode starts behaving badly. In the Explorer pane, my open folders will randomly close. If I'm in the middle of creating a file, it cancels editing the name and saves it as is, which is pretty obnoxious. It's almost like the pane is resetting.

So to summarize the issues:

  • VSCode shouldn't be randomly closing folders
  • It shouldn't require me to add a subfolder as a separate top-level workspace folder (this issue may be with the go tooling rather than vscode itself.)

Thanks for the help

VS Code version: Code 1.55.1 (08a217c, 2021-04-07T18:22:52.186Z)
OS version: Darwin x64 20.3.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 3, 3, 4
Memory (System) 16.00GB (0.74GB free)
Process Argv --crash-reporter-id 656c6348-b102-4b6b-8ade-e7f56a3faa5f
Screen Reader no
VM 0%
Extensions (9)
Extension Author (truncated) Version
vscode-eslint dba 2.1.20
go gol 0.24.0
vscode-scss mrm 0.9.0
vscode-docker ms- 1.12.1
vscode-kubernetes-tools ms- 1.3.0
remote-containers ms- 0.166.1
cpptools ms- 1.2.2
vscode-yaml red 0.17.0
vscode-proto3 zxh 0.5.3
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt700cf:30270857
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30276682
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
pythonvsnew554cf:30281909
pythontb:30283811
openwslfolder:30282073
vspre833:30267464
pythonptprofiler:30281270
vshan820:30276952
pythondataviewer:30285071
vscus158:30286553

@vscodebot
Copy link

vscodebot bot commented Apr 13, 2021

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@gjsjohnmurray
Copy link
Contributor

Does the random closing also happen with all your extensions disabled? One way to investigate this is to run the Start Extension Bisect command and follow its instructions.

@distinctdan
Copy link
Author

Thanks, I started the extension bisect, and the issue still happens on the very first step, which it said means it's a problem with vscode. Here are the specific steps I took:

  • Double click a file in the main project
  • Expand the top-level subfolder
  • Don't click anything else and wait ~10 seconds
  • The subfolder will close on its own

@isidorn
Copy link
Contributor

isidorn commented Apr 14, 2021

I can not reproduce on my machine. Might you have some file generating task in the background?
Can you reproduce with vscode insiders https://code.visualstudio.com/insiders/

@isidorn isidorn added file-explorer Explorer widget issues info-needed Issue requires more information from poster labels Apr 14, 2021
@distinctdan
Copy link
Author

I don't think I have any file generating stuff going on. I'm usually running a webpack server, but I've never seen that trigger anything in the Explorer pane when it rebuilds.

@distinctdan
Copy link
Author

I'm sorry, but I'd rather not switch to using insiders. That's unfortunate that you aren't able to reproduce it.

@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
file-explorer Explorer widget issues info-needed Issue requires more information from poster *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

4 participants
@isidorn @gjsjohnmurray @distinctdan and others