microsoft / microsoft/vscode-remote-release

vscod explora がおかしい

Open
#11,563 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Type: Bug

/a2dir/fail
/a1dir/a2dir/fail
/b1dir/b2dir/fail
中のa2dirを指定してから、それが、内包されるa1dirを指定開きすると、リストで崩れる。
dirを閉じる操作がない。

Extension version: 0.104.3
VS Code version: Code 1.113.0 (cfbea10c5ffb233ea9177d34726e6056e89913dc, 2026-03-24T15:07:18+01:00)
OS version: Windows_NT x64 10.0.26220
Modes:

System Info
Item Value
CPUs AMD Ryzen 5 PRO 4650U with Radeon Graphics (12 x 2096)
GPU Status 2d_canvas: enabled
GPU0: VENDOR= 0x1002, DEVICE=0x1636 [AMD Radeon(TM) Graphics], DRIVER_VENDOR=AMD, DRIVER_VERSION=31.0.21921.11005 ACTIVE
GPU1: VENDOR= 0x1414, DEVICE=0x008c [Microsoft Basic Render Driver], DRIVER_VERSION=10.0.26100.7859
Machine model name:
Machine model version:
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
trees_in_viz: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 31.23GB (21.16GB free)
Process Argv C:\Users\user\Desktop\新しいフォルダー\新規 テキスト ドキュメント.txt --crash-reporter-id c80eb6c7-e641-449c-84d9-b26b932488e5
Screen Reader no
VM 0%
A/B Experiments
vsliv368cf:30146710
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
6abeh943:31336334
envsactivate1:31464700
editstats-enabled:31346257
cloudbuttont:31379625
3efgi100_wstrepl:31403338
55ia6109:31457054
use-responses-api:31390855
je187915:31454425
ec5jj548:31422691
cp_cls_t_966_ss:31454198
4je02754:31466945
c3h7c220:31478652
ge8j1254_inline_auto_hint_haiku:31427726
38bie571_auto:31426784
cp_cls_c_1081:31454833
ia-use-proxy-models-svc:31452481
e9c30283:31461165
test_treatment2:31471001
ts_provider_enabled:31458190
control_6dc23131:31467998
idci7584:31464702
nes-ftch-ctrl:31485414
showingstats:31481873
534a6447:31478749
chat:31457767
8hig5102:31480529
67jbj424:31486320
bg_compact_t:31481650
t-some:31486549
cpptoolsoff-v2:31475362
db0gd219:31481871
23c7c724:31484514
client_tst_c:31484206
ddid_t:31478206

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 reported sequence in the VS Code Explorer with /a2dir/fail, /a1dir/a2dir/fail, and /b1dir/b2dir/fail: select the nested a2dir, then open its containing a1dir. Investigate the resulting list and directory-closing behavior; done means the Explorer remains correctly structured and provides a way to close the directory.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.